Ann,

> -----Original Message-----
> From: Ann W. Harrison [mailto:aharrison@...]
> Sent: Friday, November 17, 2006 5:25 PM
> >
> > Yes. I tried running the Diagnose option of IBSurgeon last night.
> > After 3.5 hours, I had to cancel the operation so as not to
> interfere
> > with the backup/restore scripts that run at midnight.
>
> OK. That's too bad. It would be nice to know which index was bad.
>

I finally got the stats. Unfortunately, this is from the database
after I rebuilt the index and a days worth of processing:

XRDS501 (332)

Index PK_XRDS501 (0)
Depth: 3, leaf buckets: 699, nodes: 426767
Average data length: 1.00, total dup: 0, max dup: 0
Fill distribution:
0 - 19% = 4
20 - 39% = 4
40 - 59% = 644
60 - 79% = 3
80 - 99% = 44

Index XRDS501_ACCOUNT_IDX (1)
Depth: 2, leaf buckets: 455, nodes: 362546
Average data length: 1.00, total dup: 0, max dup: 0
Fill distribution:
0 - 19% = 3
20 - 39% = 2
40 - 59% = 271
60 - 79% = 3
80 - 99% = 176

Index XRDS501_LOC_IDX (3)
Depth: 3, leaf buckets: 662, nodes: 362546
Average data length: 2.00, total dup: 0, max dup: 0
Fill distribution:
0 - 19% = 1
20 - 39% = 82
40 - 59% = 348
60 - 79% = 150
80 - 99% = 81

Index XRDS501_SKU_IDX (2)
Depth: 3, leaf buckets: 668, nodes: 362546
Average data length: 3.00, total dup: 0, max dup: 0
Fill distribution:
0 - 19% = 21
20 - 39% = 17
40 - 59% = 307
60 - 79% = 229
80 - 99% = 94


Bob M..