March 18, 2011 at 11:42 am
I had a server where in disks were pulled out by the network team and on one of those disks tempdb was sitting. Now i can not strt the sql server because it could not create tempdb on the given path as those drives are not avialable. How can i change the path of the tempdb to the existing drive and then start the service.
March 18, 2011 at 11:58 am
sqlservr.exe -f
Then run alter database for tempdb.
http://www.sqlservercentral.com/Forums/Topic545301-146-1.aspx
Jim
Jim Murphy
http://www.sqlwatchmen.com
@SQLMurph
March 18, 2011 at 12:13 pm
i could not start sql server from cmd line without having tempdb.
March 18, 2011 at 12:38 pm
sqlservr.exe -f -T3608
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 18, 2011 at 1:02 pm
Tara-1044200 (3/18/2011)
I had a server where in disks were pulled out by the network team and on one of those disks tempdb was sitting. Now i can not strt the sql server because it could not create tempdb on the given path as those drives are not avialable. How can i change the path of the tempdb to the existing drive and then start the service.
Steve needs to add a LIKE option on here.
Have you hunted down the NetJerk Teammember and smacked him/her yet?
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. SelburgMarch 18, 2011 at 6:47 pm
I tried all the ways above but could not start sql server. I just want to start sql server and point tempdb to an existing drive.
March 19, 2011 at 2:09 am
If you don't give us the messages you got, the chances of someone helping you are slim.
The command line to start SQL in restricted mode without bringing any DB other than master online is
sqlservr.exe -f -T3608
That should bring SQL up in a command window. You then open another command window, use SQLCMD to connect to the server and issue the alter database.
If any step of that is failing, you are going to have to explain at what point it failed and what the exact messages were. We can't see your screen and we can't read your mind.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply