Subject | Is there a way to Version stamp a Firebird schema? |
---|---|
Author | Myles Wakeham |
Post date | 2008-03-21T04:13:33Z |
I have a Firebird database that I'm going to be including with a product
that we sell. The database is used as a data warehouse for nightly "kill &
fill" from a transactional system. It also includes a lot of documentation
as to the data model, data dictionary, etc. which has been all created in a
CASE product.
I need to be able to define within the FB database, a version number
associated with the schema that was used to create the database. This way I
can be sure that we are shipping the correct DDL for the documentation.
Since users won't always upgrade at the same time, I will likely have lots
of previous versions in play and there will come a time when the
transactional system will not be able to dump its data to the data warehouse
because the data warehouse won't support key tables/columns that are needed
for reporting.
Has anyone found a way to version stamp the DDL within a Firebird database?
I can certainly do this with scripts that would build the database, but I
was hoping that since this is a Windows only product, we might be able to
ship a backup file or even a FDB file with it so that the user can get up
and running faster than having to run a script.
Any thoughts?
Myles
===============================
Myles Wakeham
Director of Engineering
Tech Solutions USA, Inc.
Scottsdale, Arizona USA
www.techsolusa.com
Phone +1-480-451-7440
that we sell. The database is used as a data warehouse for nightly "kill &
fill" from a transactional system. It also includes a lot of documentation
as to the data model, data dictionary, etc. which has been all created in a
CASE product.
I need to be able to define within the FB database, a version number
associated with the schema that was used to create the database. This way I
can be sure that we are shipping the correct DDL for the documentation.
Since users won't always upgrade at the same time, I will likely have lots
of previous versions in play and there will come a time when the
transactional system will not be able to dump its data to the data warehouse
because the data warehouse won't support key tables/columns that are needed
for reporting.
Has anyone found a way to version stamp the DDL within a Firebird database?
I can certainly do this with scripts that would build the database, but I
was hoping that since this is a Windows only product, we might be able to
ship a backup file or even a FDB file with it so that the user can get up
and running faster than having to run a script.
Any thoughts?
Myles
===============================
Myles Wakeham
Director of Engineering
Tech Solutions USA, Inc.
Scottsdale, Arizona USA
www.techsolusa.com
Phone +1-480-451-7440