Posted by: Colin Smith
Emergency, Seperation of Roles
I got a call from a customer out of state that said they needed an emergency restore of a test database. I chuckled a bit and asked what made it such an emergency. I was told that they were attempting to do some testing and the database did not have the correct data in it and they needed to load it with newer data from production. Now I know that as a DBA I want to make everyone think that there database and there problem is the most important to me. I acknowledged the predicament that they were in and I got to work to get them what they needed. I did also explain to the user that this is not an emergency since it is not affecting production but that I will always be willing to do these tasks as quickly as I can.
Then about 30 seconds after that I got a call from a local customer that needed an Emergency restore of two production databases to new database names so that both could be online. I hurried and got them restored as they asked and asked if I could do anything else to help them. They said no and then I asked why the emergency? They, the developers, have sysadmin on the instance, I have tried to fight this, and they deleted a bunch of data while developing a fix for another issue.
Now I am not really happy that I have to come in and do a restore to help them when they shot themselves in the foot. We have tried and tried to take the sysadmin role away from them but the bosses keep saying to let them keep it. Perhaps this will help us get some control back over this instance. This is a prime example of why you do not want developers developing in production.