Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 3 of 3 total |
Guid Index Compression |
Fri, Dec 8 2006 11:14 AM | Permanent Link |
"David Farrell-Garcia" | What are the recommendations for index compression in the following
index types: 1. Guid as primary index 2. Guid as foriegn key index 3. Varchar, not unique, such as customer name, address etc 4. integer field primary index 5. integer field, foriegn key 5 SmallInt field, not unique I have read the docs but want to make sure i am applying that info correctly. This app will be C/S with both LAN and WAN connections. Thanks -- David Farrell-Garcia Whidbey Island Software, LLC |
Fri, Dec 8 2006 1:43 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< 1. Guid as primary index >> Duplicate-byte. << 2. Guid as foriegn key index >> Same. << 3. Varchar, not unique, such as customer name, address etc >> Full, especially if there is a lot of blank space. << 4. integer field primary index >> None. << 5. integer field, foriegn key >> Duplicate-byte, although None might do just as well or better depending upon the actual index keys. << 5 SmallInt field, not unique >> None. Don't ever try to compress anything smaller than 4 bytes (Integer). -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Dec 8 2006 4:14 PM | Permanent Link |
"David Farrell-Garcia" | Tim Young [Elevate Software] wrote:
> David,....... Thx Tim. I guess I was on the right track. -- David Farrell-Garcia Whidbey Island Software, LLC |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |