[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

OT: Database Versioning

From: Pieter <pietercoucke_at_hotmail.com>
Date: 2007-07-13 12:11:21 CEST


My apologizes for this off-topic post, but I jsut think I will find here the
people that know the answer to my questions.

I want to start using version control for my databases too, but I don't
really know how I could do his the best. I see somehow 2 possbilities:

1. Scripting everytime the whole DataBase. But:
- Using which Tool to do this? Preferably a free (!) opensource tool?
- What if a database change forces the data to be migrated? For instances
one table is splitted in 2, and the data has to be copied and transformed:
How to do this?

2. Adding a migration script for each version in which every developer adds
the script for the changed object + script for migrating data
- What if 2 developers add something at the same time to this script? This
will cause conflicts, with potential lose of made changes?

One very important note: The solution must be very straightforard, very
easy, or things will explode here. I have some special kidn of developers,
which can't be compared to the 'normal' developers.
We use SQL 2000 and 2005.

Any help will be really appreciated, thansk a lot in advance,


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 13 12:11:13 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.