Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 3 of 3 total |
In-Memory table differences in ElevateDB vs DBISAM |
Mon, Feb 26 2007 10:27 PM | Permanent Link |
Jeff C. | The product information states this about in-memory tables in ElevateDB:
"Databases can be created entirely in-memory and can be accessed from multiple threads" I believe in DBISAM that accessing these from multiple threads was not possible, is that correct? Are there other benefits to in-memory tables in ElevateDB? |
Tue, Feb 27 2007 3:39 AM | Permanent Link |
Eryk Bottomley | Jeff
> I believe in DBISAM that accessing these from multiple threads was not possible, is that > correct? No. What you cannot do is access a memory table from multiple processes in DBISAM - multiple threads is fine, just use a dedicated session component for each thread. Eryk |
Tue, Feb 27 2007 6:41 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jeff,
<< I believe in DBISAM that accessing these from multiple threads was not possible, is that correct? > No, Eryk's response is correct. << Are there other benefits to in-memory tables in ElevateDB? >> You can have multiple user-defined in-memory databases in ElevateDB. DBISAM only allowed for one - "Memory". -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, May 4, 2024 at 09:18 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |