Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am currently experiencing this job getting stuck in my nightly maintenance solution -

ALTER INDEX [PK_ThirdPartySettleCalled] ON [evo_archive].[dbo].[ThirdPartySettleCalled]
 REORGANIZE WITH (LOB_COMPACTION = ON)

a full reindex of the table works.

but I'm using Ola Hallengren's awesome solution as I do on a number of sites that need maintenance solutions. http://ola.hallengren.com/Documentation.html and the job gets stuck in the middle of the night.

I've tested it as a single statement from within ssms with the same result, without an error I'm a little short of ideas.

Anyone experienced this issue before ?

No blocking,

the table is circa 300 million rows,

basically I say 'stuck' because no other processes are running in SQL server, and its been reorganising for hours with no error.

It is in the same state with 25% fragmentation or virutually 0% (tested after a full rebuild of the index)

share|improve this question
1  
What does "getting stuck" mean exactly? Did you investigate what the SPID is waiting on by looking at the wait type in sys.dm_exec_requests, checking for blocking, etc.? How big is the table? What is the % of fragmentation before you start the command and after you cancel because it's "stuck"? Did you observe any I/O-related entries in the system event log or SQL Server's log? –  Aaron Bertrand Aug 23 '11 at 18:25
    
@Aaron Bertrand. sorry, did't add all the things i've looked at and was still frustrated!. Within sql server - No blocking, the table is circa 300 million rows, basically I say 'stuck' because no other processes are running in SQL server, and its been reorganising for hours with no error. It is in the same state with 25% fragmentation or virutually 0% (tested after a full rebuild of the index) –  DamagedGoods Aug 24 '11 at 8:04
add comment

migrated from stackoverflow.com Aug 24 '11 at 22:41

This question came from our site for professional and enthusiast programmers.

1 Answer

up vote 3 down vote accepted

Resolved

The problem was we had a rogue cron job (unix job) related to our web servers that was using an incorrect login,

eventually it took up all 8 CPU’s so the reindex job was simply waiting for some CPU to become available before it could continue (this is why the job failed to timeout)

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.