February 16, 2010 at 2:00 pm
😉
Recently we have lots of timeouts and system issues with writing to one of our db. This db has 2 tables that are continuously in use, one table has at least one new line written to it during almost every performed action. One has over 1.88 million individual lines of data and another one has 292,000 individual lines of data currently.
Shall we archived these two tables under new names by creating a clear cut-off point (like previous seasons)? Any suggestions?
February 17, 2010 at 6:06 am
Very often Insert time-outs are as a result of Shared Locks applied by concurrent DB Read.
Things I'd check:
- Have you a lot of Indexes on these tables.
If so
Are the Indexes Fragmented
Are the Statistics up-to-date on the Indexes
- Is there some badly written read procs which are concurrently hitting your tables.
I'd also recommend the following article by Brad McGehee which enables you to use SQLProfiler to capture more info on the what's blocking when you get your time-outs.
http://www.simple-talk.com/sql/sql-tools/how-to-identify-blocking-problems-with-sql-profiler/
Good luck.
February 17, 2010 at 1:14 pm
thanks for your reply, i will start checking.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply