August 1, 2012 at 4:02 am
We have a newly built cluster environment and there is a dedicated disk for the tempdb.
Unfortunately, after the setup, I forgot to put tempdb in that drive.
so customer himself tried moving it.
Without that disk "S" being added as dependency to SQL Server resource in the cluster, customer tried to move tempdb and restarted SQL Server.
Now, SQL Server is not coming online as tempdb doesnt really exist anywhere.
Can someone help me fix this issue ASAP
August 1, 2012 at 5:54 am
Take a look at this article - http://msdn.microsoft.com/en-us/library/ms345408(v=sql.90).aspx. You can start SQL Server at special configuration (single user and only master database is up) and then issue alter database for tempdb. In order to start SQL Server with master database only, you can run this command:
NET START MSSQLSERVER /f /T3608
After SQL Server starts you can run the alter database statement, and then restart the server.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 1, 2012 at 6:03 am
Issue resolved now.
the service account running SQL Server didn't have permissions on the clustered Disk "S"(in our case) to create temp mdf and ldf files.
After we have full permission to the service accounts, tempdb got created and we were able to start sql server.
Another issue that I sense here is that the customer wanted to create Tempdb mdf and ldf files in the root directory(S:)
I guess, had he created the tempdb in a folder within S Drive like S:\Tempdb, the permission issue wouldn't have happened.
Can someone pls confirm if the root directory of any drive needs special permissions?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply