October 15, 2010 at 7:07 am
Hi,
I have a Active/Passive cluster running Windows 2K3 SP2 & SQL 2K5 SP2 - All 64 bit.
Currently, we have all the database files on the F: drive of this cluster, but we are slowly running out of space.
We already have a G: drive in the cluster too, and I was going to add another file to the Primary filegroup until we can arrange for more storage to be installed.
I've tried to add this via the GUI, and the G: does not appear in the list of drives, when I script this off to done and run the script:
ALTER DATABASE DatabaseName
ADD FILE ( NAME = N'DatabaseName_Data1',
FILENAME = N'G\MSSQL\DATA\DatabaseName_Data1.ndf' ,
SIZE = 3072KB , FILEGROWTH = 1024KB )
TO FILEGROUP [PRIMARY]
I get the error:
Msg 5105, Level 16, State 2, Line 1
A file activation error occurred. The physical file name 'G\MSSQL\DATA\DatabaseName_Data1.ndf' may be incorrect. Diagnose and correct additional errors, and retry the operation.
Msg 5009, Level 16, State 8, Line 1
One or more files listed in the statement could not be found or could not be initialized.
I'm a bit confused as to the cause of this.
Any help? Please?
Dave
October 15, 2010 at 7:32 am
Aha!
I think I've found the problem.
It looks like that the G: isn't a dependency of SQL Server.
Now I have to figure a way to add this without taking the resource offline, as it's a live environment.
October 15, 2010 at 7:43 am
You need to have a downtime. In Sql server 2005 one cannot add the dependency without taking the sql server service offline.
October 15, 2010 at 7:54 am
That's what I suspected.
Thank you.
Dave
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply