Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
Table partitions |
Mon, Apr 14 2008 9:13 AM | Permanent Link |
DavidS | Hi,
Does ElevateDB support table partions like sql does? If not what is the best way to design a system where tables can have millions of records all which require searching, even with indexing? Regards, David |
Mon, Apr 14 2008 3:48 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< Does ElevateDB support table partions like sql does? If not what is the best way to design a system where tables can have millions of records all which require searching, even with indexing? >> The quick answer is no. However, ElevateDB partitions each table into ..edbtbl, .edbidx, and .edbblb files, which helps cache locality and keeps each portion of the table smaller than if they were all dumped into the same file. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Apr 15 2008 5:36 AM | Permanent Link |
DavidS | What is the best way to design a system where tables can have millions of records all which require searching, even with indexing?
"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote: David, << Does ElevateDB support table partions like sql does? If not what is the best way to design a system where tables can have millions of records all which require searching, even with indexing? >> The quick answer is no. However, ElevateDB partitions each table into ..edbtbl, .edbidx, and .edbblb files, which helps cache locality and keeps each portion of the table smaller than if they were all dumped into the same file. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Apr 15 2008 6:08 AM | Permanent Link |
"Jose Eduardo Helminsky" | David
The number of records does not matter *IF* the searchs will occur in the indexed fields. Could you give us a little example of what exactly you want ? I have some applications with 3Mb records and I do not have any problems with searching on there. Eduardo |
Tue, Apr 15 2008 7:42 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | David
You might find that searching isn't the problem, adding records is, or if you have a fragile environment and (say) duff network connections or wobbly power cause corruption it might be the time to repair. ElevateDB is faster than DBISAM but as always, as Jose is saying, it depends on a specific case. So if you can publish some details it would help. While my tables are nowhere near that large I do know one individual who used DBISAM for the UK postcode database in an app. After a bit of tweaking of how he searched it speed was good. Roy Lambert [Team Elevate] |
This web page was last updated on Friday, September 20, 2024 at 05:39 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |