|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Implementing Version Control on Database ScriptsI am looking for best practises, procedures, dos-don'ts, and tools for implementing version control on a database development project. Three items need to be tracked: 1) code (stored procedures and user-defined functions) 2) database schema 3) data (lookup-table data and test data) The development environment will have a master database managed by a single DBA. Each developer workstation will hopefully install a daily build which will include an updated database. There will be three enviroments: development, test, and production. Thanks in advance for any help. Cheers, Frank J. Reashore, MCSD.net, MCDBA Vancouver, Canada Frank J. Reashore wrote:
> I am looking for best practises, procedures, dos-don'ts, and tools for Hello,> implementing version control on a database development project. You might find useful a script I made in Ruby, to extract all database objects. It allows to enter it in a version control tool. You can also schedule it regularly and run a diff tool on the results to track changes. The blabla on the page is in french, but the code is easy to understand : http://www.babaluga.org/doku.php/programmation/comparaison_python-ruby Have also a look at Abaperls : http://www.abaris.se/abaperls/ A collection of perl scripts by Erland Sommarskog |
|||||||||||||||||||||||