 |
 |
Archives of the TeradataForum
Message Posted: Wed, 11 Nov 2015 @ 18:17:37 GMT
| Subj: | | Re: Change History of Table Structure |
| |
| From: | | Aldrin, John |
There is no way that the database keeps track of DDL Changes. However, many sites use a Source Code Control System to capture their DDL code
that is used to promote from Development into their Test and Production environments.
The Source code management system can provide the level of change data capture you are looking for. In our case, we don?t capture every change
in the DEV environment, just the final version that will be promoted. There is no real need for any final granularity. When we are ready to
promote the DBA team will receive a list of objects and then extract all of the DDL into individual files (DDL, Comments, Statistics, etc.) and
then run them through a standardization process. This standardization change all views, macros, procedures to use the REPLACE syntax, change our
database names from EDW_DEV to EDW_${TDENV} so that we can dynamically promote using Linux Shell Scripting techniques. We also remove the
FALLBACK and BEFORE/AFTER JOURNAL statements from the CREATE TABLE files since we want those to be inherited from the Target Database definition.
We also generate a BUILD script for every object that uses Shell commands to assemble the individual components (DDL, Comments, Statistics, etc.)
into the final migration script. There is also a Master Build script that dictates the actual sequence the database objects are installed to deal
with dependencies and prerequisites.
E. John Aldrin
| |
