Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread DBISAM 3 or 4
Fri, Aug 28 2009 11:44 AMPermanent Link

"Bobby Gallagher"
Hi

This may have been answered before but I cannot find the answer

I have both V3 and V4 of DBISAM and also Elevate DB.  All of my applications
are written for DBISAM V3 and we have been hoping to move straight to
Elevate DB but don't have the time just now to do that. Would we benifit in
the short term by moving to DBISAM V4 - I think that this should be an easy
and quick upgrade.  Just wondering what the advantages in doing that would
be

Regards

Bobby

Fri, Aug 28 2009 1:05 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Bobby,

<< I have both V3 and V4 of DBISAM and also Elevate DB.  All of my
applications are written for DBISAM V3 and we have been hoping to move
straight to Elevate DB but don't have the time just now to do that. Would we
benifit in
the short term by moving to DBISAM V4 - I think that this should be an easy
and quick upgrade.  Just wondering what the advantages in doing that would
be >>

Moving from DBISAM 3 to 4 will require table upgrades and possibly some
changes to the SQL and code, so while it is easier than moving to ElevateDB,
it isn't a very simple process either.  With that in mind, and the fact that
you plan on moving to ElevateDB anyways, I would wait and just make the
switch when you're ready.

Also, in case you didn't know, we can provide assistance with the conversion
process to ElevateDB.  Just contact me via email if you're interested.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Aug 28 2009 3:01 PMPermanent Link

Raul

We faced the same dilemma and it really depends on your code-base, short-term vs long-term
requirements and time constraints.

Based on my opinion (some sample coding projects with ElevateDB, reading manual and of
course this newsgroup)  the switch to ElevateBD is fairly major one in learning the
product and also how you do things differently now. It's definitely the  modern solution
but will likely result in some short-term pain in getting everything re-written from
DBISAM and working again.

In our case we could not afford the time required to build own EDB knowledge and change
all the code. So we went with DBISAM4 - we had most of the DB code in a couple of
centralized units and migration was actually quite painless. Definitely read the
differences document and test, test, test.

We do still plan to move to EDB eventually but for now DBISAM4 provides a supported DB and
we can maybe even wait for EDB Enterprise Smile

Just my $0.02

Raul
Image