Rebuild index on MS SQL server takes forever

Question

1.00/5 (1 vote)

See more:

Hello friends,

I have a strange problem in a MS SQL Server 2014:
- Insert or even selecting a row into/from 1 specific table fails. It takes forever!
- sp_who2 does not show blocking SPID's
- dropping an INDEX? forget it
- rebuilding the index? forget it
- DBCC CHECKDB: No Issues

Any familiair with these symptoms?

What I have tried:

- Insert or even selecting a row into/from 1 specific table fails. It takes forever!
- sp_who2 does not show blocking SPID's
- dropping an INDEX? forget it
- rebuilding the index? forget it
- DBCC CHECKDB: No Issues

Posted 13-Jan-22 3:06am

Herman<T>.Instance

Updated 13-Jan-22 9:06am

Add a Solution

Comments

_Asif_ 13-Jan-22 9:13am

How many rows present in this table? And share the estimated execution Plan of the select query.

Herman<T>.Instance 13-Jan-22 10:01am

33900

_Asif_ 13-Jan-22 10:24am

Its not possible that 33900 rows cause SQL Server to go nuts. There must be some level of locks present that caused this issue. You need to Re Start SQL Server services and try executing the select query again

Herman<T>.Instance 13-Jan-22 10:45am

Hi _Asif_
After restart of the DB everything runs smooth again. In 4 weeks time this issue returns.
- Sp_WHo shows no blockedby's
- dm_tranlock might show a record
Cannot find this issue!

CHill60 13-Jan-22 9:29am

Showing details of the index would also be useful.

Herman<T>.Instance 13-Jan-22 10:39am

CREATE NONCLUSTERED INDEX [idxTest-TestProgramPart] ON [TDMS].[tests]
(
[test_program_parts_id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = ON, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 80, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
GO

Herman<T>.Instance 13-Jan-22 10:24am

We saw a hanging item in the dm_tranlock, removed it and select worked again

CHill60 13-Jan-22 11:39am

Does comment mean your issue is now fully resolved?

Herman<T>.Instance 16-Jan-22 15:00pm

It will return in 4 weeks time

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

RickZeeland · Accepted Answer · 2022-01-13T09:06:00

Solution 1

Try this free maintenance tool: SQL Index Manager – Free GUI Tool for Index Maintenance on SQL Server and Azure[^]

Posted 13-Jan-22 9:06am

RickZeeland