I'm a sysadmin who has recently been landed with some SQL DBA responsibility. Not reluctantly I might add, this is a world I'm very much looking to get immersed in.
I am curious about one of the aspects of our existing setup (where DBA tasks were previously largely left to the developers), namely the update mechanism for one of our production databases.
Essentially what happens is that any time the underlying data changes, one of the developers creates a new database in the dev environment and restores it onto the production environment. To facilitate this the development team have been given dbcreator permissions. This happens once or twice a week.
Can any of the more experienced DBAs spot any flaws with this approach? Should I insist on handling all the restores myself (I have written out the T-SQL commands for the dev team to use instead of SSMS which required sysadmin rights to browse the available media)? Could something go wrong during a restore that would knock the database offline?
We're using SQL Server 2008 R2 standard edition.