Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Trying to reorganise an index, the reorganise indexes dialog seems to hang. Which scares me a bit. I'm running SQL Server Standard 2005. The screen has been like this for about 9 hours. The animation on the bottom left is running. What should I do? How long might this take?

Any help would be greatly appreciated!alt text

share|improve this question
    
With that kind of fragmantation you should Rebuild it by the way, is there any Large Object on you table (like a varchar(max))? If not you can Rebuild online. If you rebuild you will get updated statistics. –  Gabriel Guimarães Nov 9 '10 at 12:55
1  
I should rebuild, but I can't have the table going down, and SQL Standard can't rebuild online. –  Martijn Nov 9 '10 at 14:11

1 Answer 1

Wait. Check what goes on on the server using the dynamic queries. How large is the table? Seriously - rorganize index CAN take a LONG time if your disc subsystem is not up to the task and the table is large large large. i unce had an UPDATE statement that ran like 40 hours.

So, what does the server say (cpu, disc io load)? Anything happening?

How large is the table (number of rows)?

share|improve this answer
    
6.2 mil rows, no trouble on the CPU (10ish %), trouble on the IO-load (hits 100% at times for a few seconds, then dips way down again and hovers around 15% for a while) –  Martijn Nov 9 '10 at 11:03
    
6.2 millions? Well what is the size of each row... ? Is that controlled by Resource Governor? –  Gabriel Guimarães Nov 9 '10 at 12:56
    
Yeah. IO spikes suond like it is just... taking time. 10% CPU... how many cores? Could well be 1 core running full speed (8 cores assuming). –  TomTom Nov 9 '10 at 13:41
    
10% cpu is typical for us. When I'm checking it's not one core maxing out –  Martijn Nov 9 '10 at 14:33
    
How many cores do you have? one maxing out will never show like that - before 2008 R2 server - because of the scheduler moving the load around. –  TomTom Nov 9 '10 at 21:53

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.