标签云

微信群

扫码加入我们

WeChat QR Code

In our current database development evironment we have automated build procceses check all the sql code out of svn create database scripts and apply them to the various development/qa databases.This is all well and good, and is a tremdous improvement over what we did in the past, but we have a problem with rerunning scripts.Obviously this isn't a problem with some scripts like altering procedures, because you can run them over and over without adversly affecting the system. Right now to add metadata and run statements like create/alter table statements we add code to check and see if the objects exists, and if they do, don't run them.Our problem is that we really only get one shot to run the script, because once the script has been run, the objects are in the environment and system won't run the script again.If something needs to change once it's been deployed, we have a difficult process of running update scripts agaist the update scripts and hoping that everything falls in the correct order and all of the PKs line up between the environments (the databases are, shall we say, "special").Short of dropping the database and starting the process from scratch (the last most current release), does anyone have a more elegant solution to this?