Hi,
I'm running 4 instane SQL Server 2005 in an active/passive clustered
enviroment utilizing a SAN.
I'm running out of space on one of my LUN's for one particular instance.
This instance was originally set up as follows:
LUN 1 - Database partition (3 databases) - K drive
LUN 2 - Log Partition - L drive
LUN 3 - Backup Partition - M drive

I've now added another LUN to this Resource Group within cluster
administrator. The server correctly see this new LUN which is my S drive,
however the Management Studio does not see this LUN.
I detached a database and moved it from the K drive to the S drive, but when
I tried to reattach the database I could only see the K, L and M drive I
could not see the S drive.
Any idea why this is happening?

Thanks in advance,
D7

You need to make the SQL service dependent upon the new disk. SQL
clustering won't allow you to store data on drives that are not on the
dependency list.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"d7" <d7 (AT) discussions (DOT) microsoft.com> wrote

Thank you Geoff, that makes sense, I shall try out of hours tonight.


"Geoff N. Hiten" wrote: