Can there be a great way to check database structure right into a SVN? Possibly checking inside a DDL file when transformed?

Any ideas?

I have never tried it, only one of individuals might answer your question (unsure, haven't read them completely)

Sure, but unless of course it's strictly a development database you'll most likely likewise incorporate some data-migration programs between versions. You will want to have the ability to have total freedom to decrease posts, meaning you will want to have the ability to bring everything back later if design needs require them. For any better instance of the reason, take a look at how Rails handles migrations.

Maintaining a DDL script that may produce the database on your own, including default information is employed by me at this time. It causes it to be pretty simple to generate more compact upgrade scripts from revision to revision at the appropriate interval having a simple diff.

I began just a little project some time to maintain database updates in an exceedingly simple file that could then be maintained a lengthy side out source code. It enables easy updates to designers in addition to UAT and Production. The tool creates but Sql Server and MySql.

Some project features:

  • Enables schema changes
  • Enables value tree population
  • Enables separate test data card inserts for eg. UAT
  • Enables selection for rollback (not automated)
  • Keeps versioning on SQL server and Mysql
  • Is able to import your overall database into version control with one easy command

The code is located on the internet code. Take a look at Google code for more information

You can handle your DDL scripts in SVN, nevertheless, you never make sure that the DDL scripts in SVN repository are representing the accurate picture of the database schema. The reason being your developer can update the SVN repository without altering the database or vice verse, update the database without update SVN repository.

I suggest you have a look on dbMaestro Working together for Oracle. The product may be the only Database Version Control which enforce change policy within the database level. It forces your designers to do check-out and appearance-directly into object to be able to change them within the database.

Their site is: http://world wide

For oracle database we use oracle-ddl2svn tools.

It automated next process

  1. for each db plan get plan ddls
  2. place it under version contol

Provide lots of designs via fundamental command line options or advanced XML configuartion

The tool Lure causes it to be simple to extract all of your Oracle database source code (DDL and PL/SQL) to some files to ensure that you can include it to the file based version control system like SVN or Resumes. Additionally it may instantly deploy exactly the same source files to a different database instance. The merchandise website reaches