Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 Database Design and Application Architecture
 Handling high volume data

Author  Topic 

Starting Member

1 Post

Posted - 2007-04-18 : 23:23:58
Hi Guys,

I am facing problems with concurrent access in SQL Server 2000,The scenario is that the DB contains one huge de-normalized table containing 40 million records.

The application frequently queries this table to populate other derived tables,the sql queries take a long time to return results.

So if one query is in execution the other user's query goes into a
wait mode.Please suggest how I can better this.

Or do I need to upgrade to 2005.


Master Smack Fu Yak Hacker

2507 Posts

Posted - 2007-04-19 : 00:25:40
IDentify the long running queries. Identify the columns in the WHERE condition of those queries. Do you have indexes on all/most of those columns?
Also, do you have regular maintenance jobs re-indexing/updating stats for that table.

Life is short. Enjoy it.
Go to Top of Page

Master Smack Fu Yak Hacker

2886 Posts

Posted - 2007-04-19 : 00:26:08
is this large table written to often, or only read from? if you only read from it, you can add appropriate indexes without penalty to improve the selects. use profiler to find out which queries are slow, then have a look at the query plan of those selects to see what indexes would improve them.

alternatively you can try the index tuning wizard, see what it suggests.
Go to Top of Page

- Advertisement -