By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,087 Members | 1,508 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,087 IT Pros & Developers. It's quick & easy.

Suddenly, queries against one table "never return"

P: 1
I've got this 20,000 row table. It had never given anyone trouble. I'm not a particularly good SQL Server admin, but I'm all we have. I was certified on MSSQL 7, some years ago, but it's just a sideline job.

Anyhow, about 5 months ago, I was out of town, and a consultant at my site who was apparently a very good MSSQL guy was covering for me. This one table "went crazy". Queries against it, even the Enterprise manager "open table" and "return top 1 row" times out. It turns out that someone reported this problem to the consultant guy, who told them "we need a little reorg". He did something, the problem went away, and I never heard that this happened.

Now, the problem has recurred, and I have no idea what could cause this. The MSSQL log shows nothing interesting. It's just this ONE table. Can anyone help here? What could be the problem? What "reorg" do you think the consultant did? How do you suggest I fix this silly thing now?
Jan 25 '08 #1
Share this Question
Share on Google+
1 Reply


ck9663
Expert 2.5K+
P: 2,878
I've got this 20,000 row table. It had never given anyone trouble. I'm not a particularly good SQL Server admin, but I'm all we have. I was certified on MSSQL 7, some years ago, but it's just a sideline job.

Anyhow, about 5 months ago, I was out of town, and a consultant at my site who was apparently a very good MSSQL guy was covering for me. This one table "went crazy". Queries against it, even the Enterprise manager "open table" and "return top 1 row" times out. It turns out that someone reported this problem to the consultant guy, who told them "we need a little reorg". He did something, the problem went away, and I never heard that this happened.

Now, the problem has recurred, and I have no idea what could cause this. The MSSQL log shows nothing interesting. It's just this ONE table. Can anyone help here? What could be the problem? What "reorg" do you think the consultant did? How do you suggest I fix this silly thing now?
just to have you back up and running ASAP, try to re-creating your table and insert back all your rows....then create an index. remember: if a table have only 1 index, it's always recommended it to be clustered....

-- ck
Jan 25 '08 #2

Post your reply

Sign in to post your reply or Sign up for a free account.