Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
Table Record Size (DBISam 4) |
Mon, May 11 2009 11:38 PM | Permanent Link |
"Adam H." | Hi,
I was just curious - when it comes to designing DBISam tables, does the record size really affect performance (excluding table rebuilds, etc). I'm aware that each new field will add to the size of the table (on disk) by the size of the record multiplied by the records in the table. In my instance I have a table with up to 100,000 records. Adding 10 GUID fields will increase the size used by disk significantly (compared to the existing size of the table, considering that the new fields may only be used in 20% of cases). I'm not overly worried about the space used on disk, nor the rebuild times - as long as normal performance isn't going to get a hit. I was wondering if I should be putting these new fields in a separate table and joining them together via queries, or if it's fine to keep adding these fields to the existing table? Cheers Adam. |
Wed, May 13 2009 2:43 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Adam,
<< I was just curious - when it comes to designing DBISam tables, does the record size really affect performance (excluding table rebuilds, etc). >> After a certain point, yes, but probably not with 100,000 rows. My estimate of an addition of 10 GUID columns is around 38MB extra space in the .dat file portion of the table, which won't be a killer. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |