August 25, 2009 at 9:36 am
Hi I desperately need your help. I moved the TempDB to another drive and now sql service won't start. It'll start but stops immediately. I have tried to run it with the local system account and also with my domain account but no luck. All this was as a result of the the mdf file getting too big, the drive was 50GB and the mdf file was just about 50GB so we decided to move the tempdb off the drive and that's when all hell broke lose ... any suggestions?
BTW ... When I try to bring sql up in dos by running sqlservr > -c -f -T3608 -T4022 -
I get 'Error: Instance name exceeds maximum length Aborting Initialization'
August 25, 2009 at 9:41 am
pls give details of the process used to move tempdb files .... that would be helpful in giving a solution. Also - is this SQL 2000 or 2005 or 2008 ??
did you check the startup parameters on the SQL Service. you could check that in properties of the service, where it basically defines the location of the Master database's mdf and ldf files and the location of the SQL Error logs and if any startup trace flags. go to the error log location and try to open it to check if there are any distinctive errors there... that might give yo a hint....
-------------------------------------------------
-Amit
Give a man a fish and he'll ask for a lemon. Teach a man to fish and he wont get paged on weekends !! :w00t: - desparately trying to fish [/size]
August 25, 2009 at 9:45 am
Have you tried moving it back? Also I see you are running in minimal config mode, have you tried -m for single user, not sure it will make a difference.. I know this should work for 2005/2008 not sure in 2000.. Use the -s paramter..
CEWII
August 25, 2009 at 9:46 am
Amit Kumar Singh (8/25/2009)
Also - is this SQL 2000 or 2005 or 2008 ??
It is a SQL 7/2000 group..
CEWII
August 25, 2009 at 10:26 am
This is SQL 2000 and this is the command I used to move the Tempdb
USE master;
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = tempdev, FILENAME = 'C:\Tempdb\tempdb.mdf');
GO
ALTER DATABASE tempdb
MODIFY FILE (NAME = templog, FILENAME = 'C:\Tempdb\templog.ldf');
GO
Now I found out that the reason I couldn't get sql to start in dos was cause I was adding the server name when I only needed to put the instance name (hence the error the instance name exceeds maximum length).
Once I made the change SQL is trying to come up except I keep getting this error 1105, severity : 17, state: 2
"Could not allocate space for object 'alert' in database because the PRIMARY filegroup is full.
September 25, 2009 at 4:25 pm
Is this resolved?
Mj
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply