Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL Slow to start when rebooting server

Status
Not open for further replies.

AndrewBaines

Technical User
Apr 19, 2002
463
GB
I'm having a problem with SQL 2008 taking ages to make the databases available. Master, model etc are available very quickly, but the rest of the databases can take nearly a minute to accept connections.
This means that an application on the server that needs to connect to the server won't start. I've got a temporary workaround by using delayed on the service startup.
I've tried turning off AV and increasing server RAM. Neither made any difference.

Any ideas?
Thanks
Andrew

Andrew Baines
 
How big are the databases (mdf files)?

How big are the log files (ldf files)?

Are there any messages in the SQL error log during shutdown? What about windows error log? Any sign that its not cleanly shutting down?

Just wondering if its not shutting down correctly and then having to replay a log file (or something similar) and running a check database.

Not an expert on this - just a hunch!

Dan

----------------------------------------

Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind - Bernard Baruch

Computer Science is no more about computers than astronomy is about telescopes - EW Dijkstra
----------------------------------------
 
Are the drives that the user databases on local drives or are they external (SAN, etc) drives?

If they are external drives....something may be slowing the server down from connecting to or recognizing the external drives.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875
 
Thanks for the quick responses - to answer you both:
It's a really simple install - the databases being loaded are tiny (MB, not GB), they're all stored on a local drive. No security is setup beyond only allowing a single user to connect. You really couldn't get any simpler - the database only needs a local connection.
No problems shutting down.

Andrew Baines
 
Have you looked in the SQL Server Error Log to see if it indicates where the issue might be? When you reboot, the new log will usually show that there are transactions being rolled back or forward, database being checked (CHECKDB being run), etc.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top