|
|
Posted by Mork69 on 01/30/07 09:24
As Erland says, it's a very good idea to store your SQL object under
source control. We have written tools to make the process of keeping
your changes under source control and propagating them to your test
and production environments simple and straightforward. Please see
www.dbghost.com for more details.
Some great advantages of this way of doing things are:
1. A 100% audit trail of who changed what, when and why (source
control history)
2. Scales to hundreds or even thousands of developers
3. Saves developer time writing upgrade or delta scripts - the tool
does it for you
4. SQL changes can be properly synchronized with the other code
changes via changelists (atomic checkin)
5. Branches are easily compared for differences when you are comparing
the object CREATE statements rather than hand coded ALTER scripts.
I hope you like our approach :)
Regards,
Malcolm
On Jan 29, 11:48 am, d.gra...@gmail.com wrote:
> We are trying to use source control to store our database objects and
> queries in Perforce. The general idea is to produce scripts which
> create all objects in the DB and then store the SQL in source control.
> Has anyone done this before and can suggest some advice? Alternatively
> if anyone has other methods for using source control on a database,
> could you please let me know?
>
> Also, is there any automated way of extracting individual scripts for
> object creation from the database?
Navigation:
[Reply to this message]
|