I’ve touched a lot of SQL Servers over the years. After my share of trips to HR for inappropriate touching, here’s the questions I ask first these days:
- Is this in production now?
- If this goes down, what apps go down with it?
- When those apps go down, is there potential for loss of life or money?
- How sensitive are these apps to temporary slowdowns?
- When was the last successful backup?
- When was the last successful restore test?
- Is everyone okay losing data back to the last successful backup?
- When was the last successful clean corruption test?
- Do we have a development or staging environment where I can test my changes first?
- Is there any documentation for why the server was configured this way?
- What changes am I not allowed to make?
- Who can test that my changes fixed the problem?
- Who can test that the apps still work as designed, and that my changes didn’t have unintended side effects?
This -> “After my share of trips to HR for inappropriate touching”
Jumped straight out at me :-O
Great list! I also like to add “Who do I talk to if I have questions?” And I want at least a DBA, a Dev and a business person if at all possible.
“8.When was the last successful clean corruption test?” -> Is this something other than using DBCC CHECKDB?
Here is a few more questions I like to ask.
Is there any type of replication in place and if so can I stop it while troubleshooting?
Those are actually very useful questions to ask when you’re given access to fix anything IT-related, from installing software on a desktop PC to receiving commit privileges on a source control repository…
Very nice list! I would add is there any historical data on performance over the past quarter or since the last major upgrade.
I like this list. I tend to ask my question 1 again in between every other question.
In this questionnaire i have question!!
How would you test you changes done for whole system slowdown problem in test\dev server instead of Production server?!
Today our support team worked with a customer installing a database update to our product at their site. Something had gone wrong and they were trying to restore the DB backup that occurs at the start of the update process. No problem, right? Well they couldn’t find the backup. After an hour of investigation they found another DBA had noticed the server getting low on space and “fixed” the problem by deleting the just-completed backup.
I’m thinking the DBA hadn’t ready your post.
I’d add “Who can we contact on the storage team, and are they cooperative?”
Great list Brent!