These days I'm doing 'Development' Database Administration. And I'm posting about updates to QA Databases.
We're a development department. We have several Development Databases and several QA Databases. It's all for the same Application but a few different Databases for a few different Customers. We currently have QA Databases 'locked down' i.e. Developers can not modify Stored Procedures in QA. They must modify them in the Development Database and then they notify me to promote them.
We used to be in more of a "build" cycle, i.e. several developers would modify several stored procedures in dev and about once a week, a new build of the Application would be created and I would move all the modified Stored Procedures to QA so that the new build could be tested. And that was working well. Now we're in more of a 'patch' cycle, i.e. I get about 5 requests per day, each to move just 1 Stored Procedure to QA, so just that fix or change can be tested. So this has become very tedious and distracting, having to drop what I'm doing to carry out too many small requests.
Was hoping for feedback or suggestions. Any ideas for me? Are your QA Databases locked down? Should I consider lifting the permissions on the QA Databases so that Developers can promote the Stored Procedures themselves?