If you had a DBA that was responsible for deploying a database in a live environment, then what would you like to choose will do? A database creation script or a backup that he can restore to an existing database? What types of advantages / disadvantages are there? (We're using MSSQL2000 and MSSQL2005)
When I use a database of John's I agree with the first deployment suggestion Backup, I like the idea of a script available for review to check at least coding standards, performance evaluations, etc.
If you are looking at some things that have already been reviewed, then backup / restore is an ideal option for deployment before, and even more if the configuration data is in that database "Staged" helps in avoiding long or complex converged statements.
Earlier releases are going to be scripts. In our environment we require release notes to specify the path for the server, examples and scripts. The scripts should be provided in numerical order, with the second set of rollback scripts, separated into folders by the target database. We also need that in each script, the US The statement is at the top so we are not concerned about creating a new object in the master database! ;)
Comments
Post a Comment