Hi

I've got 3 applications, one 16-bit Delphi 1 using BDE, one 32-bit Delphi 5
using BDE, and one Delphi 5 using an MS Access database.

I'd like to migrate all to either DBISAM or ElevateDB. Also, I'm in the
progress of migrating to Delphi 2007.

I need the apps to run as single user or many (up to 5) users with the
database on a server.

As my users are located remotely, I need the data migration from BDE and
Access database to be fully automatic.

For one of my apps, it is a single user app only, but relies hevely on fast
access to database, so I'm looking for ways to use in-memory tables.

What are the considerations when choosing between DBISAM or ElevateDB?

Thanks
Jacob

Jacob

Both DBISAM and ElevateDB have utilities to convert from BDE, I don't think either have from Access but I could be wrong. To convert the access database you'd need to get it into some form that could be imported.

Both DBISAM can operate in either fileserver or clientserver modes and both come with a 5 user server.


Both have in-memory tables. DBISAM has a single in-memory database that you can have as many tables in as you want, ElevateDB can have multiple in-memory databases each of which can have many tables.

So far about the same.

"Issues" with ElevateDB
For me there are a number of issues with ElevateDB (mainly caused by Tim following the SQL:2003 standard), but since you're not coming from DBISAM most will not affect you. The ones that might are:

In DBISAM NULL is the same as an empty string, in ElevateDB it is not. There are various strategies to work with this (the most popular I guess is defaulting string fields to empty string) and various issues eg: .Clear & .IsNull

In ElevateDB VARCHAR fields are no longer right trimmed before being stored

If you have a lot of SQL code then you will want to review this against both DBISAM and ElevateDB

The final issue which WILL affect you is the move from storing the table definitions in the table to in a catalog. Its not difficult when you get your head round the concept but it seems to have given a few people a headache.

Conversion of your app will almost certainly be easier with DBISAM. It was written as a BDE replacement and when I switched to DBISAM V2 several years ago the conversion was almost only altering TTable to TDBISAMTable etc. ElevateDB is a bit more "heavy metal" and has different concepts.

If you're used to one of the pure play SQL databases then ElevateDB is definitely for you.

If you're prepared to invest a bit of time and effort to learn ElevateDB's features (substantially based on adherence to the SQL:2003 standard) then it will pay off - its faster than DBISAM and it is the product that will continue to be developed. Alternatively if you want a quick and easy conversion with minimal effort DBISAM will be the best one.

What you could do is download the trials of each product, pick one of the BDE based apps and try the conversion with each.


Roy Lambert [Team Elevate]

Hi,

You should be able to convert your access database by setting up an ODBC
connection to your data in the BDE and importing the data that way.

Regards
Trevor Keegan

Roy,

<< Both DBISAM and ElevateDB have utilities to convert from BDE, I don't
think either have from Access but I could be wrong. >>

ElevateDB has an ADO migrator, so it can natively convert any ODBC/ADO/OLEDB
data source.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


><< Both DBISAM and ElevateDB have utilities to convert from BDE, I don't
>think either have from Access but I could be wrong. >>
>
>ElevateDB has an ADO migrator, so it can natively convert any ODBC/ADO/OLEDB
>data source.

I'm glad to be wrong

Roy Lambert [Team Elevate]

Thank you for your replies. I'll go for ElevateDB

Cheers
Jacob