Comments on: Playground or Not, That Is the Question! http://sqlrus.com/2012/04/playground-or-not-that-is-the-question/ Wed, 17 Apr 2013 13:48:14 +0000 hourly 1 By: John Morehouse http://sqlrus.com/2012/04/playground-or-not-that-is-the-question/comment-page-1/#comment-258 John Morehouse Tue, 03 Apr 2012 15:42:55 +0000 http://sqlrus.com/?p=855#comment-258 Mike - I completely agree. Our environment is setup much like yours, where the developers only have true rights in Dev & Stage (although our QA world is completely separate) and only reader rights in Integration & Production. I just thought that it was interesting point of view that was taken. I tend to treat QA just like production, since that's the environment that mimics exactly what should be in true Production. Thanks for your thoughts! Mike – I completely agree. Our environment is setup much like yours, where the developers only have true rights in Dev & Stage (although our QA world is completely separate) and only reader rights in Integration & Production. I just thought that it was interesting point of view that was taken. I tend to treat QA just like production, since that’s the environment that mimics exactly what should be in true Production. Thanks for your thoughts!

]]> By: Mike Fal http://sqlrus.com/2012/04/playground-or-not-that-is-the-question/comment-page-1/#comment-257 Mike Fal Tue, 03 Apr 2012 15:25:22 +0000 http://sqlrus.com/?p=855#comment-257 My company has 3 or 4 environments, depending on the app: Dev - Developer work space Stage - QA environment Integration - Customer facing QA Prod Of these, the only one I consider a true playground is Development. In there, I'll grant developers SA (with care) and allow them to adjust backup and maintenance jobs. They can also create databases at will. The assumption is that if they blow their foot off, it's their own damn fault, i.e. that's the one bullet Barney Fife gets. Any other environment is hands off. Because we need to maintain a consistent QA environment, control over Stage and Integration is almost as strict as production. My company has 3 or 4 environments, depending on the app:
Dev – Developer work space
Stage – QA environment
Integration – Customer facing QA
Prod

Of these, the only one I consider a true playground is Development. In there, I’ll grant developers SA (with care) and allow them to adjust backup and maintenance jobs. They can also create databases at will. The assumption is that if they blow their foot off, it’s their own damn fault, i.e. that’s the one bullet Barney Fife gets. Any other environment is hands off. Because we need to maintain a consistent QA environment, control over Stage and Integration is almost as strict as production.

]]>