Promotion to Production
-
What methods do you use for promotion to production? Does anyone have any opinions/suggestions? The company I work for has to have separation of duties for SOX Compliance. Developers are not allowed to promote anything to production. We have to supply either MSIs or scripts to SAs who then promote the web-app to production. The problem we are having is with database changes. What is the best way to turn over either an entire database or specific objects to the DBAs to have them promote it without modifying it? We currently either tell them where an object is on a development server and have them copy it from there or we provide them a .sql file and tell them what machine to execute it against. The way they do it now, they may miss permissions or remove permissions because of either not following directions or dropping existing objects instead of altering them. Any recommendations would be greatly appreciated. Thanks, JB
-
What methods do you use for promotion to production? Does anyone have any opinions/suggestions? The company I work for has to have separation of duties for SOX Compliance. Developers are not allowed to promote anything to production. We have to supply either MSIs or scripts to SAs who then promote the web-app to production. The problem we are having is with database changes. What is the best way to turn over either an entire database or specific objects to the DBAs to have them promote it without modifying it? We currently either tell them where an object is on a development server and have them copy it from there or we provide them a .sql file and tell them what machine to execute it against. The way they do it now, they may miss permissions or remove permissions because of either not following directions or dropping existing objects instead of altering them. Any recommendations would be greatly appreciated. Thanks, JB
jonathanburris wrote:
The way they do it now, they may miss permissions or remove permissions because of either not following directions or dropping existing objects instead of altering them.
I follow this route with all of my database changes. It means that the script must also include the permissions. My applications all use ROLES for permission setting, so that simplifies things a lot. Additionally, my script files are also kept under source control. So the hand off can take place through a source control system. Obtaining SOX compliance may be seen as the end benefit, but the truly greater benefit, is that you end up with an implementation process and you no longer rely upon one individual to perform some action. With large, complex systems, you are avoiding many headaches this way.
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]