LS,

We're still using dbIsam 3.3 which served and serves us -and more important:
our customers- very, very, well. We had plans for upgrading to dbIsam 4 but
there just was no need for it. But, well, like Dylan said: "the times they
are changing". But now I noticed that there soon is to be a new phenomon:
EDB. So I have a few questions about the new elevateDB, regarding to us now
using the 'old' 3.x version of dbIsam:

-will there be a (huge) gain in speed?
-will there be a tool to upgrade tables from dbIsam 3.x to elevateDB
-is there a lot of 'recoding' needed
-is there a lot rewriting of SQL statements needed?
-what would be the main advantages to upgrade?

Regards, Harry

Harry

Tim is the only person who will be able to answer this fully but here's my 2p from things already posted

>-will there be a (huge) gain in speed?
No - there will be some gains but I doubt there'll be a "huge" gain in normal operation

>-will there be a tool to upgrade tables from dbIsam 3.x to elevateDB
Yes - unless Tim suffers a commercial blackout

>-is there a lot of 'recoding' needed
I don't think there'll be a lot (at least not my definition of "lot")

>-is there a lot rewriting of SQL statements needed?
Oh yes - refer to the discussion on NULL for starters, then there's single quote vs double quote since you're coming from V3

>-what would be the main advantages to upgrade?
Good question - I'll let you know after I have, but from Tim's postings
- a move to fail safe writes
- catalog support
- better sql

Roy Lambert

Roy Lambert wrote:

> > -will there be a tool to upgrade tables from dbIsam 3.x to elevateDB

> Yes - unless Tim suffers a commercial blackout


I have asked that very same question some time ago and Tim answered
that EvelevateDB would upgrade v4 tables only.

A huge amount of my customers are running with v2 tables. Not being
able to upgrade those directly to ElevateDB format is the main reason
why I probably won't buy ElevateDB.

Jan Derk

use v4 Dbsys to ugrade 3 to 4 then EDBsys to upgrade from v4
whats the problem ?
Rita

"Jan Derk" <none@none.none> wrote in message
news:xn0et3ejm7ghxl5000@news.elevatesoft.com...
> Roy Lambert wrote:
>
>> > -will there be a tool to upgrade tables from dbIsam 3.x to elevateDB
>
>> Yes - unless Tim suffers a commercial blackout
>
>
> I have asked that very same question some time ago and Tim answered
> that EvelevateDB would upgrade v4 tables only.
>
> A huge amount of my customers are running with v2 tables. Not being
> able to upgrade those directly to ElevateDB format is the main reason
> why I probably won't buy ElevateDB.
>
> Jan Derk

R. Tipton wrote:
> use v4 Dbsys to ugrade 3 to 4 then EDBsys to upgrade from v4
> whats the problem ?

in the fact you couldn't deploy an automatic upgrade procedure to the
customers!!!
You should force each of them to send you their archives (imagine the
privacy problems involved in some cases), upgrade them manually, then send
new tables back to them, or, alternatively, force them to manual upgrade
tables (and customers are usually able to make the worst damages even in the
simplest cases).

Sandra

Couldn't one include both the DBISAM v2 (or v3) compenents and the ElevateDB components into a single Delphi app. and simply transfer the data
into the ElevateDB tables?  This could be done in your regular app., in a separate conversion utility application, or in a DLL that you include.

"Sandra" <sandra70it@gmail.com> wrote:

R. Tipton wrote:
> use v4 Dbsys to ugrade 3 to 4 then EDBsys to upgrade from v4
> whats the problem ?

in the fact you couldn't deploy an automatic upgrade procedure to the
customers!!!
You should force each of them to send you their archives (imagine the
privacy problems involved in some cases), upgrade them manually, then send
new tables back to them, or, alternatively, force them to manual upgrade
tables (and customers are usually able to make the worst damages even in the
simplest cases).

Sandra

Jan,

<< I have asked that very same question some time ago and Tim answered that
EvelevateDB would upgrade v4 tables only. >>

That's what I said initially until you brought up the issue with 2.x.  My
response was this:

http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=5&msg=55977&page=1#msg55977

--
Tim Young
Elevate Software
www.elevatesoft.com

Greg,

<< Couldn't one include both the DBISAM v2 (or v3) compenents and the
ElevateDB components into a single Delphi app. and simply transfer the data
into the ElevateDB tables?  This could be done in your regular app., in a
separate conversion utility application, or in a DLL that you include. >>

That's basically what the migration code does, although it also translates
the table metadata and creates the necessary ElevateDB tables, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sandra,

<< in the fact you couldn't deploy an automatic upgrade procedure to the
customers!!! >>

Actually, you could do all of what Rita mentioned in code without user
interaction.

--
Tim Young
Elevate Software
www.elevatesoft.com

Harry,

<< -will there be a (huge) gain in speed? >>

Not huge, but certain things like the SQL will be faster.

<< -will there be a tool to upgrade tables from dbIsam 3.x to elevateDB >>

Yes, there will be migration components available.

<< -is there a lot of 'recoding' needed >>

Most likely, there will be at least a medium amount of recoding required,
specifically with SQL and with DDL operations like creating tables and
altering tables.

<< -is there a lot rewriting of SQL statements needed? >>

It depends, but most likely yes.

<< -what would be the main advantages to upgrade? >>

Better database manager, better user security, better SQL support, better
catalog support, SQL/PSM support in the form of stored procedures,
functions, and triggers, Unicode support, better collation and
multi-language support, and managed .NET support (although Win32 support
will be first out of the gate).

--
Tim Young
Elevate Software
www.elevatesoft.com