|P is for Practical|
Re: DDL Parsingby gsiems (Chaplain)
|on Aug 05, 2011 at 03:40 UTC||Need Help??|
I wasn't aware of any back when I had the question/problem... so, many years ago, I rolled my own. I'm still not aware of any other scripts so I've been continuing to use the home-rolled solution. FWIW, I recently revisited and re-wrote portions of it to use git for tracking the changes-- this allowed me to throw out much of the original custom code.
While it isn't the most elegant code I've ever written, it works well enough and it isn't so ugly as to make my eyes bleed looking at it. The current incarnation is built around the dbms_metadata package, sqlplus, git, perl, shell, and cron.
The work flow is more-or-less as follows (for each database of interest, with each database having it's own git repository):
This runs once a week from cron on a linux box (could run it more often but weekly is sufficient for our purposes).
I'm pretty pleased so far with using git to track the changes-- so pleased I've even gone so far as to twist git to document the DDL differences between our production, test, and development databases. The work flow for documenting the differences operates along the lines of (for each pair of databases to compare):
...at this point the comparison git repository has but two commits, the "from database" and the "to database" and git kindly indicates the new, deleted, moved and changed db object DDL files.
I don't have this anywhere out on the net but you can drop me a line if you're interested in looking at it.