single resource in the Cluster Management tool. C: is local and unique to
each machine so it cannot be a shared resource. SQL setup will create the
correct dependencies. If you add a disk later, you will need to adjust the
SQL Server to be dependent on the new disk resource. SQL Setup will also
Geoff N. Hiten
"dmcmillan via SQLMonster.com" <u18500@uwe> wrote in message
news:6b18263878bd3@uwe...
>I have read that document and it is very helpful, but I do still have a
> couple questions. I see that the drives on our servers don't exactly
> correspond to the physical disks, so I:,J:,Q: will be added as one
> physical
> disk type resource I guess.
> The C: drive is not available as a choice when trying to add it as a
> physical
> disk resource even though we have set it up on the servers. Any
> idea why that might be and how I can get it?
> What dependencies should physical disks have assigned?
> Also, should the SQL Server Agent be added as a resource, if so what type
> and
> dependencies should we use?
> Thanks so much for all help!
>
> Geoff N. Hiten wrote:
>>Try this: It is a bit long, but I think it covers pretty much everything
>>in
>>settint up a cluster.
>>
>>
http://searchsqlserver.techtarget.com/searchSQLServer/downloads/SQL_Cluster_Ezine_Final_needs_URL.pdf >>
>>>I haven't set up a failover cluster before and hope someone can help.
>>> It is Windows 2003, SQL Server 2005 failover cluster. We have set up 2
>>[quoted text clipped - 13 lines]
>>> Also what dependencies should they have?
>>> THanks for any ideas!
>
> --
> Message posted via SQLMonster.com
>
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-clustering/200612/1
>