Re: Problems with SQL Server 2005 Install on Cluster

ebferro wrote:
Jeffrey:
That's a good point. I don't know the answer to that question since I've uninstalled SQL Server 2005 to reinstall and try over again. However, on the previous install, the installation created the SQL Server instance and IP address for SQL Server. I don't think it automatically assigned both drives as a dependency for SQL Server. I will install SQL Server again and manually add Drive G as a dependency to SQL Server after the installation. Thanks for the tip as I think this is going to solve my problem.
Ernie

"Jeffrey Williams" wrote:

ebferro wrote:
I think I'm having a problem with a cluster install of SQL Server 2005. I have two drives on a raid array. Array 1 is designated as Drive G and the second array is Drive H. I want the log files to go to Drive G and the database files to go to Drive H. During the install, if I select the advanced parameters, I can designate that the database files go the Drive H and they do go there. If I run the configuration after the installation, there is an option there to designate where the log files go. When I select that option, the only drive choice that comes up is drive H. I've also tried changing the startup parameter, the -e parameter in the line that starts up the SQL Server service. When I change this to G:\Logs the subdirectory to which I'd like the log files to go, the SQL Server service no longer starts and I get access denied errors in the error log. I've added the groups that I assigned to the SQL Services during installation to the security on the drive and also gave those groups full control of the drive and still no joy. Does anyone know why the G: drive does not show up as an option in the configuration when I select a location of the logs after installation or does anyone know how I can designate that the logs go to the G drive during installation? And, yes, both Drive G and Drive H are members of the SQL Server resource in the cluster. TIA

But, are both drives listed as dependencies for SQL Server?


The install will only make the SQL Server resource dependent upon the installation drive. So, in your case you are installing on H:, so that drive is added. The install doesn't know anything about the G: drive and it is not added.

Note: you have to take the SQL Server resource offline to add dependencies.

Jeff
.

Relevant Pages
Loading