December 19, 2002 at 4:30 am
Any change request or new devlopment requires update on production server and it is always a sensitive task. DB changes are implemented on production server in various ways.
What are the common practices??
1. Keep track of all changes manualy and make a script.
2. Compare production DB with development DB with inhouse developed utility and make a script manully.
3. Compare both DB's using third party freeware utility and make a script manually.
4. Use Third Party tool to fully compare and update automatically.
Share your experience!!!
December 19, 2002 at 4:57 am
Combination of the two. For small changes the developers send me the script. FOr larger ones I use 3rd party to show the differences, then review the changes with the developer, generate a script from that.
Andy
December 19, 2002 at 9:44 am
December 19, 2002 at 10:56 am
You may consider using ERwin (AllFusion) to find all the differences between two databases and generate code that would syncronize them. As far as I can tell from my experience, ERwin is very treliable in this regard. It will generate SQL code to make all the changes. It will also give you a visual representation of all the differences down to attributes, constraints, indexes, triggers, SP, etc.
December 19, 2002 at 12:30 pm
I found that AdeptSQL works great for comparing two databases. Does script generation, etc. Pretty short money <$500 for a 4-user license.
Regards,
Chris
December 19, 2002 at 12:55 pm
My wife wrote her own utility to compare two databases. Then I built on it for myself and used when ERwin was not available. It is easy considering that everything is in the system tables. The hard part is to cover EVERY difference between two databases (SP, veiws, triggers, etc.). That is when ERwin (or other tools?) helps.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply