Problem solve
Get help with specific problems with your technologies, process and projects.
Maintain large SQL Server database and resolve website 'Timeout Error'
If you have exceptionally large SQL Server databases, refer to these best practices for proper database maintenance to steer clear of a website 'Timeout Error.'
We have a large database on the "live server" with about 5 GB out of which 1.5 GB space is allocated by transaction log files. Also, our website executes 20,000 to 25,000 insertions daily. Occasionally, the website gives a 'Timeout Error' because this time database process gets locked or blocked. What is the best way to maintain such a large database?
There are a few things you should consider. You'll want to look at the queries which are causing the blocking. Usually this will be a SELECT statement which doesn't have the WITH (NOLOCK) option on it, or an UPDATE statement which is running against the database.
Continue Reading This Article
Enjoy this article as well as all of our content, including E-Guides, news, tips and more.
Step 2 of 2:
You can also look and see how much free space your database has and how often the database is extending the database. If the extend size is too large, this can cause database queries to timeout. With the database file being only 3.5 GB this probably isn't all that likely unless the disk drives are too overloaded. You can check to see if the disk drives are being overloaded by using performance monitor and checking the disk queue, reads per second and writes per second.
This was last published in March 2008
Dig Deeper on Microsoft SQL Server Performance Monitoring and Tuning
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our SQL Server experts
View all SQL Server questions and answers
Start the conversation
0 comments