×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
My client has a large partitioned file defined as an SQL Table, which has 3
different Indexes defined.
Size of one of the index size is about 3 times that of the others. We were
trying to figure out why, and whether anything can be done about it.
Record length : 381 bytes (no variable length or date format fields)
Index 1 : Key length 60 bytes (Fields A - 18, B - 9, C - 15, D - 15, E -
packed 5,0) - Unique
Index 2 : Key length 61 bytes (Fields A - 18, B - 9, C - 15, D - 15, X -
packed 7,0)
Index 3 : Key length 64 bytes (Fields Y - packed 7,0, A - 18, B - 9, C -
15, D - 15, E - packed 5,0)
No selection on either index, so number of index entries on all is the same.
Index 1 is about 223 GB, Index 2 is about 151 GB, Index 3 is about 680 GB
Any ideas?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
