Hi

Could anyone just give me a quick clarification on the upgrade process between versions. I have my app working just fine and to go from, say, 2.11 to 2.15. Upgrading the components recompiling the application and deploying a new server.

If there are changes the the internal structure of the data files, how is this handled?

For example to go between firebird or SQL server database versions requires a backup and restore to update the database format to a newer correct version.

I've never had a problem and it just works every time, but I'm just wondering if I'm not doing something I should be.

Thanks in advance.

Chris,

<< Could anyone just give me a quick clarification on the upgrade process
between versions. I have my app working just fine and to go from, say, 2.11
to 2.15. Upgrading the components recompiling the application and deploying
a new server.

If there are changes the the internal structure of the data files, how is
this handled? >>

The ElevateDB table file formats never change, but occasionally the database
catalog format does change.  However, every new version of ElevateDB can
read older catalog formats transparently.  The only thing to worry about is
if the database catalog is *updated* with a newer version (DDL such as
CREATE, ALTER, DROP).  In such a case, the catalog format will change to the
newer version and older versions of ElevateDB will see a version error when
they try to open the database, specifically:

Error #100  The object has been updated by a newer version of the engine

You can see what version any given database catalog has been updated to by
issuing the following query:

SELECT * FROM Configuration.Databases

The column that you want is the CatalogVersion column.  It will match the
last release number that updated the database catalog format.  For example,
the last time the catalog format was changed was in the 2.05 release, so
most of my database catalogs report that version.

You can also see this in the ElevateDB Manager on the properties page when
you select a database node.

Now, of course, this all excludes *special* upgrade steps, such as what
occurred with the latest 2.15 and the Unicode/ANSI changes.  In such cases,
it will be a requirement to run special utilities to change around certain
settings, etc. due to design changes in how ElevateDB works.   But, this is
normally pretty rare.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Nice timing Chris, as I was about to ask the same thing…

Tim, for making it clear to me, the following step are required to go from 2.11 to 2.15

1.Recompile application with 2.15 components…
2.Backup current 2.11 database (just as a precaution, not REALLY needed)
3.Replace edbsrvr.exe with new 2.15
4.Apply the 2.15 fix utility
5.Finish.

Do I got it right?

regards,
Mario

Mario,

Yes, that's it.

--
Fernando Dias
[Team Elevate]

Hi Tim

Thanks for that, just what I needed.