I get strange behavior when I install 2005 into a cluster. I have 2 disk
resources (on a SAN) that I have added to a SQL group. When I install 2005,
I don't ever specify to use the log disk, I only tell it to put the data on
the data disk. The strange part is, after it installs, the log disk is a
viable resource for SQL and is added to the dependency group for it, but the
data drive isn't available. I have to add it to the dependency list of SQL,
before it's available. (Not to mention, it doesn't actually install
anything to the Data disk, it only installs to the Log disk.)
Anyone know why it's not putting my data on that drive and why it's not
adding it to the dependency list?
Now I have to move all my DB files to the data drive, what a pain.
Anthony Thomas - 26 Jan 2006 02:08 GMT
Does the Log Disk show up first in the drive list?
When you install, you can specify which drive to use, but usually, you can
only install to one drive. Additional drives have to be manually configured
afterwards and before you start creating databases.
Sincerely,
Anthony Thomas
> I get strange behavior when I install 2005 into a cluster. I have 2 disk
> resources (on a SAN) that I have added to a SQL group. When I install 2005,
[quoted text clipped - 9 lines]
>
> Now I have to move all my DB files to the data drive, what a pain.