Sql Server EXTREMELY Slow to start
-
Ok...I've got a client who is on SQL 2000 SP4. When the server that Sql is installed on is rebooted it can take 7 - 12 minutes before Sql Starts. I have Sql Server and Sql Server Agent both set to autostart. This is a pretty fast machine so something has be wrong for it to take this long to start. There are only 6 databases (Besides northwind, pubs, etc...) that are installed. Any advice is really appreciated.
Ryan Grant
Financial Systems Consultant
Elypsis, Inc
ryan@elypsis.com -
What account do you use for the services? If you're using a domain account and you have networking issues, the SQL startup can be impeded while the security credentials are verified.
Is there any messages in the Windows Event Log?
--------------------
Colt 45 - the original point and click interface
-
We are using the local system account to login. This might make a difference, the client is not using a domain. They are using a workgroup. It doesn't seem to affect the use of the databases at all. Once sql is started, it works fine.
Ryan Grant
Financial Systems Consultant
Elypsis, Inc
ryan@elypsis.com -
If anyone has anything additional to add I would really appreciate it. I am really stuck and would love to be able to improve the startup timee of Sql. 10 minutes is unacceptable.
Ryan Grant
Financial Systems Consultant
Elypsis, Inc
ryan@elypsis.com -
1) Does it have a lot of recovering (rolling forward transactions) to do (see sql server logs)
2) It might be because of the tempdb is growing to its initial size
3) Anything in the eventviewer / sql server logs?
-
What is the recovery interval set to?
EXEC sp_configure 'recovery interval'
-
I have a server that has 4 1GB processors and has a 205+GB database on a SAN.
It can take 15 - 20 minutes to come up. That's normal for the amount of data. It has to bring up each table individually, do any rollbacks and checks necessary before it comes completely up.
To narrow down the delay....turn the SQL Server services off (disable them). Restart the server and time it. Reset the SQL Server services to what they should be and restart the server, again timing it.
That will give you an idea of where the delay is at and then you can start working on solutions.
-SQLBill
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply