Work requests: It’s broke. Fix it.

Many years ago I was given a work request that literally just said:

It’s broke. Fix it.

I’m sure you can see how that is supremely unhelpful. And this isn’t the only time I’ve gotten such great requests.

I need full access.

Please run this script.
(I’ve even gotten this one without an attached script.)

Job abcdef failed.

Now, because a post that does nothing but complain is equally unhelpful here are a few things you should always include in a request to a DBA.

What do you need? In detail please. The SQL Server instance. And the actual name, not some random alias that your team uses. If there is more than one give me a list. Database(s). Same thing as above. I don’t necessarily know what database you are working with today. If it’s not going to be dbo then I need to know what schema(s) you are working with. If you want access then I need to know what access you need. In detail. Read, Write, Create Objects, etc. And if you just put admin and no details as to why then the answer is just No. Give me details. If I’m running a script then make sure the script is available. Make sure you tell me what instances/databases to run it under. I’m aware that some scripts are going to have a USE statement at the top. If so, and it doesn’t match what you tell me here then be prepared for questions.

Continue reading on SQLStudies.com.

54321
(0 votes. Average 0 of 5)