Subject | Re: [IB-Conversions] Re: MS SQL 2 InterBase Wizard |
---|---|
Author | Helen Borrie |
Post date | 2000-08-30T12:23:37Z |
At 01:12 PM 30-08-00 +0200, you wrote:
to do it. Creating it interactively is about the worst.
As you go on through you database development, you simply add your ALTER
DATABASE, CREATE TABLE, ALTER TABLE, etc. statements to the script and
continually keep a completely rebuildable metadata script available - which
also serves as your front-line system documentation.
Cheers,
Helen
http://www.interbase2000.org
___________________________________________________
"Ask not what your free, open-source database can do for you,
but what you can do for your free, open-source database."
(J.F.K.)
>I would like the following idea: Optional output to an ASCII fileAbsolutely - creating the entire database from a script is the proper way
>which contains the whole SQL code to build the database. This file
>could be used as input for isql. If there are any problems you can
>use an editor to make some changes. This could increase the chances
>to get the beast migrated. The programming effort for the wizard
>shouldn't be very high because I expect that the statements have
>just to be stored into a file instead of throwing them to the server.
>
>Kind regards
>
> Andreas.
to do it. Creating it interactively is about the worst.
As you go on through you database development, you simply add your ALTER
DATABASE, CREATE TABLE, ALTER TABLE, etc. statements to the script and
continually keep a completely rebuildable metadata script available - which
also serves as your front-line system documentation.
Cheers,
Helen
http://www.interbase2000.org
___________________________________________________
"Ask not what your free, open-source database can do for you,
but what you can do for your free, open-source database."
(J.F.K.)