Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 4 of 4 total |
Index Compression |
Thu, Jun 15 2006 2:15 PM | Permanent Link |
Sean McCall | Tim,
Based on a post you made in another newsgroup I just looked at the index compression document and I have a suggestion for ElevateDB. It would be nice to have the default option for new tables to be automatic/smart compression. Have the database engine apply the rules you lay out in this document to select the best index compression model based the types and order of fields in the index. Naturally anyone could still override these compression methods, but for those who use it out of the box the indices will most likely be optimized. The document you referenced was: http://www.elevatesoft.com/dbisam4d5_index_compression.htm Thanks, Sean |
Fri, Jun 16 2006 2:44 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Sean
You're to late - in a "teaser" Tim has already said ElevateDB (aka DBISAM2007 will have automatic optimisation of index compression Roy Lambert |
Fri, Jun 16 2006 10:06 AM | Permanent Link |
Sean McCall | Excellent
Roy Lambert wrote: > Sean > > > You're to late - in a "teaser" Tim has already said ElevateDB (aka DBISAM2007 will have automatic optimisation of index compression > > Roy Lambert > |
Fri, Jun 16 2006 12:46 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Sean,
<< Based on a post you made in another newsgroup I just looked at the index compression document and I have a suggestion for ElevateDB. It would be nice to have the default option for new tables to be automatic/smart compression. Have the database engine apply the rules you lay out in this document to select the best index compression model based the types and order of fields in the index. Naturally anyone could still override these compression methods, but for those who use it out of the box the indices will most likely be optimized. >> What Roy said. To give a little more information - the index compression is automatically on for non-unique keys, and doesn't require decompression/compression for every page read/write. IOW, the compression is done in-place and on-the-fly. This is actually pretty damn hard to do and still maintain performance with the .NET managed code restrictions on how it can be coded, and it took most of January and February to get it done. That's one of the biggest chunks of time that wasn't planned on originally. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Thursday, April 18, 2024 at 10:42 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |