asked on New drive in SQL-cluster
Hi,
We were lacking diskspace on our SQL-cluster (F-drive) and added a new one (H-drive).
Then we detached a database and now want to attach it. However, the H-drive is not visible when we choose "attach". I read somewhere you can set the default location of database so new database will go to the new drive, but this seems a bit tricky. Won't SQl look for all its database on the H-drive then?
I would prefer to just reattach from H-drive, moving database by database.
Thanks for your feedback.
We were lacking diskspace on our SQL-cluster (F-drive) and added a new one (H-drive).
Then we detached a database and now want to attach it. However, the H-drive is not visible when we choose "attach". I read somewhere you can set the default location of database so new database will go to the new drive, but this seems a bit tricky. Won't SQl look for all its database on the H-drive then?
I would prefer to just reattach from H-drive, moving database by database.
Thanks for your feedback.
Microsoft SQL Server 2005
Last Comment
EvilPostIt
Is H: drive local?
ASKER
Yes, it's a local drive (SAN).
The defalt database location is only for new databases.
In cluster adminstrator make the new h: a dependency of the SQL Server service. SQL will not allow you use drives that are not a dependency.
In cluster adminstrator make the new h: a dependency of the SQL Server service. SQL will not allow you use drives that are not a dependency.
ASKER
Thanks, are you absolutely sure about this? It's a production environment in which I cannot take any risk.
Is there any Microsoft-article 'bout it?
The reason why I ask, is what you mention about the dependency.
I don't thinks this is correct. If I look in the properties of our F-drive (on which current databases reside) there is no dependency set. This config is working for some years, we had some reboots, power cuts etc and the cluster came up without any issues.
Is there any Microsoft-article 'bout it?
The reason why I ask, is what you mention about the dependency.
I don't thinks this is correct. If I look in the properties of our F-drive (on which current databases reside) there is no dependency set. This config is working for some years, we had some reboots, power cuts etc and the cluster came up without any issues.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Ok, so the dependency is set on the SQL-server.
However, we have to bring it down to set the dependency????
=> "Right Click on SQL Server, select Take Offline."
So, in order to add a new disk, we have to bring down our production SQL-cluster???
There should be another way, we cannot just bring down our cluster ....
However, we have to bring it down to set the dependency????
=> "Right Click on SQL Server, select Take Offline."
So, in order to add a new disk, we have to bring down our production SQL-cluster???
There should be another way, we cannot just bring down our cluster ....
This is the way it works. There is no other way.
Are you happy with the proposed answer or do you require further assistance?