J
James Palmer
Guest
Going back to this thread, again. I'm doing a test D&L of a customer database because they have index corruption meaning it's as good a chance ad any to do this for them. The vast majority of tables have dumped and loaded very quickly, but some haven't. One table in particular is very large and I want to try and select a better index for the dump. Ignoring which index is the most used int he application, how would I use this dbanalys output to decide on the quickest index for the dump? PUB.Entrylocatn confirmed 173 7 3 60195 468.4M 100.0 1.0 Confirmed-JobId 617 2 3 10510 81.7M 99.8 1.0 Confirmed-OrigJobId 618 2 3 10508 81.7M 99.8 1.0 confirmed-trx-reference 174 3 3 60551 471.1M 99.9 1.0 cross-dock 175 8 3 34898 271.5M 99.9 1.0 entrylocatn 176 6 3 98477 766.2M 99.9 1.0 GTIN 619 1 3 10443 81.2M 99.8 1.0 location 177 5 3 115438 897.5M 99.9 1.0 Pallet-No 620 1 3 15015 116.8M 99.9 1.0 pending 178 5 3 33938 264.1M 99.9 1.0 picker-stats 179 3 3 10451 81.2M 99.8 1.0 picking-daily-stats 180 3 3 10451 81.2M 99.8 1.0 po 181 1 3 10445 81.2M 99.8 1.0 SSCC 621 1 3 10443 81.2M 99.8 1.0 transaction-reference 182 1 3 36455 283.7M 99.9 1.0 unique-item-number 172 5 3 87428 680.3M 99.9 1.0 unit-set 183 2 3 12704 98.8M 99.9 1.0
Continue reading...
Continue reading...