Re: Splitting Data and Logs
- From: "John Vandervliet" <jvandervliet@xxxxxxx>
- Date: Wed, 25 Apr 2007 13:04:12 -0600
Neil,
ok I think you did that wrong, add the disks that are not showing up as dedencies to the SQL server resource, you will need to stop the SQL service first then go to properties of the SQL Server service and modify the dependencies tab so that each of the missing drives shows up under Resource Dependencies for the SQL Server Properties.
That should do the trick.
Use the following to see if SQL instance is actually seeing the drives.
select * from ::fn_servershareddrives()
John Vandervliet..
Open the cluster admin tool
"Neil Paddock" <NeilPaddock@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:378CC919-885B-4C52-9167-6624799A23DE@xxxxxxxxxxxxxxxx
I have set the dependencies on the logs disk resource but still can't see it
under the database properties in SSMS?
I have restarted cluster services on both nodes - is there anything else I
have missed?
Thanks,
Neil Paddock.
"Geoff N. Hiten" wrote:
You must add the disks to the resource group for your SQL Server AND make
the SQL service dependant on them.
Once you have this configured, SQL will display and allow these disk devices
to be used for database file storage.
You can use SSMS to change the default location once the dependencies are
set correctly.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Neil Paddock" <NeilPaddock@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E96CD8BB-AA4E-49EE-B454-14BFA1316805@xxxxxxxxxxxxxxxx
>I am having difficulty setting up my disks on my SQL 2005 cluster. I >have
>a
> data disk and log disk for each instance (3) but when trying to setup a
> new
> DB, when I try to choose the log drive it does not appear.
>
> I remember choosing a location during setup for data files and this is
> what
> is displayed.
>
> How do I go about splitting my data and log files for each database
> instance?
>
> Thanks,
> Neil Paddock.
.
- Follow-Ups:
- Re: Splitting Data and Logs
- From: Neil Paddock
- Re: Splitting Data and Logs
- References:
- Re: Splitting Data and Logs
- From: Geoff N. Hiten
- Re: Splitting Data and Logs
- Prev by Date: Re: Commit of internal MSDTC transaction failed: Result Code = 0x8004d
- Next by Date: Re: Default or named instances??
- Previous by thread: Re: Splitting Data and Logs
- Next by thread: Re: Splitting Data and Logs
- Index(es):
Relevant Pages
|