RE index rebuilds

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Walter Vaughan
> Sent: Wednesday, June 29, 2011 1:51 PM
> To: filePro
> Subject: Re: RE index rebuilds
> 
> Richard Kreiss wrote:
> 
> >One of my clients has a procedure the rebuilds auto indexes at night.
> >
> >The procedure has gone from 45 minutes to about 2 1/2 hours.

This time is for 8 separate files comprising about 60 indexes built on
multiple keys.
> >
> >
> Don't your clients run windows?

Yes, and on a fast server.  Re-indexing the file above took 3 1/2 minutes on
the server and 18 minutes on the terminal server server.

> 
> >One file has 6 auto index ranging in size from 11MB to 76Mb.
> >
> >
> My experience on *bsd is that would take 45 seconds to 2-1/2 minutes :)
> 
> .. the real problem is disk. Here's something that I have ran into
recently with
> similar problem and MS-SQL. NTbackup was not completing and it was not
> obvious what the culprit was. It was jamming up disk IO but not affecting
> CPU.
> 
> Here's what you want to google... "Average Disk Queue length"
> Become an expert on that... then you will know exactly what is going on
and
> what is *really* making it take so long.
> 
> Honestly MS does have enough tools to debug this. It's just stuff that you
> never worry about on the client side, so experience for the average
> sysadmin is limited.

Thanks for the suggestion.  I will look at this but I am not the sysAdmin
for this system.  They have an outside company managing their system.

Richard