Author Topic: Migration Script Generation (DDL)  (Read 3478 times)

Viking

  • EA User
  • **
  • Posts: 453
  • Karma: +2/-2
    • View Profile
Migration Script Generation (DDL)
« on: June 24, 2014, 02:25:39 am »
Dear experts,

We currently use “TOAD Data Modeler” (TDM) and we consider the switch to EA (because we plan to use EA also for other purposes).

A nice feature of TDM is the migration script generation:

  • In TDM we are versioning data model versions “old fashioned” with version extensions to the file name. We are currently using only physical data models.
  • Let’s assume an example where we start with data model version 1.0.0 (current version in PROD) and throughout the development (on DEV) we are creating several subsequent versions, of which some are deployed only to DEV, selected ones are deployed to TEST and usually only the final one is deployed to PROD.
  • TDM allows you to just specify a base version and a target version of the data model and generates the DDL and migration scripts (!!!) which need to be deployed / processed to bring the database from base to target version. This includes e.g. renaming of an old table, creation of the new table, move of the data from the old to the new table and finally the delete of the old table. All this is created by TDM “out of the box”.
  • This feature allows us to easily and flexibly create the migration scripts we need. E.g. on DEV you go from 1.0.1 to 1.0.2 to 1.0.3 to … to 1.1.0. On FAT and PROD you go directly from 1.0.1 to 1.1.0. No coding / script development required any more, just a short review / check of the generated script does it.
This TDM “out of the box” feature generates very easily the DDL and migration scripts we need and thereby enables us to be very flexible and efficient with different variations of deployments. Furthermore, this is the “enabler” and motivation to apply all changes only in the data model. It ensures that the data model is always up-to-date and not by-passed for “little” changes over time.

If we would need to give this up, we would be forced to go back to manual development / coding of DDL and migration scripts, leading to higher efforts, less flexibility, higher risk of errors and therefore more test and bug fixing efforts.

So my question is, is there a solution provided by EA?

V
« Last Edit: June 24, 2014, 02:53:52 am by Viking »

skiwi

  • EA Expert
  • ****
  • Posts: 2081
  • Karma: +46/-82
    • View Profile
Re: Migration Script Generation (DDL)
« Reply #1 on: June 27, 2014, 01:52:09 pm »
In the base product I suspect YAGGI (cf YAGNI).

You might like to see if http://www.dbmode.com/ has what you want, or can be persuaded to provide it.

Good luck, I'd like it too
Orthogonality rules
Using EA16.1 (1627) on Windows 11 Enterprise/64 bit. Repositories in SQLServer2019 DB Schema 1558.
WebEA on Pro Cloud Server 4.2.64

Viking

  • EA User
  • **
  • Posts: 453
  • Karma: +2/-2
    • View Profile
Re: Migration Script Generation (DDL)
« Reply #2 on: July 21, 2014, 09:25:54 pm »
Quote
In the base product I suspect YAGGI (cf YAGNI).

You might like to see if http://www.dbmode.com/ has what you want, or can be persuaded to provide it.

Good luck, I'd like it too

Hi skiwi,

many thanks for your suggestion. Very welcome.

My understanding is that dbmode does not generate DDL and migration scripts. Am I wrong?

Best regards

V