Hi,

Has anyone come up with a good practice of maintaining the scripts for installation for production database and Upgrade from there on.

Can I have your great ideas here on this? I do carry on with a preset practice of using batch files and .sql files called in batch files and thus having it installed and upgraded. Versioning and maintaining scripts and releasing for testing are all kind of difficult.

If someone has a better way of handling this, please let me know here. Also this will help a lot of other working in DB domain.

Replies and thought are much appreciated.
Cheers

_________________________
- Vijay G
Strive for Perfection

__________________
- Vijay G

On Unix I do this well. But on Windows since it requires "point and click" generally to install information its a lot harder. I have seen some people use QA like tools that similate pointing and clicking for consistency in the windows world. In linux you write a shell script to do it all and then run a standardized shell script across servers. You can also take screen shots with every (point/click/input string) you require for installs/upgrades. Unfortunately this still needs to be done by a human......

Just some ideas.