As DBA's, we are responsible for the full life of the data at our hands. We need to make sure data is backed up, readily available in an acceptable format, in a timely fashion. Even when data is deleted, it's our responsibility to make sure we do not need it and we have back ups of the data just in case.
Another big job is handling requests from leaders who like to see their numbers in different ways.
A typical question a DBA might encounter is, Can I get the revenue for last fiscal year?
Below are a list of questions I like to ask when handling requests for data.
1. Is the data going to be used internally, or externally?
This is very important as to how the data might be used. Is this for a Survey that will ultimately decide an industry ranking?
2. How is the data going to be used?
Is this for an audit? Is this for projections? Is this for performance evaluations? This can help you determine how accurate the data needs to be.
3. Who is asking you for the data?
Sometimes it's a good idea to get everyone in a room to talk about what exact data is needed. I've seen so many times how an original request evolves after you have talked to everyone involved.
4. Is someone asking the person asking you?
Again, keep asking until there isn't anyone else involved with your particular data question at hand. Plus, it's always nice for your boss’s boss to see who's actually doing the work.
5. Is this a request we have fulfilled before?
No reason to re-invent the wheel. Consistency is a good thing.
6. If so, who gave you the data last time?
Go talk to that person and find out what issues they had. Ask if they were asked to re-run the numbers for any given reason. Ask him or her for the SQL they used.
7. Can I have a copy of the data provided to you last time for comparison?
This will give you the ability to provide the data in the same format and you can use this to help ballpark your accuracy.
8. Please understand, even though the bottom line numbers should be the same, some project attributes may have changed since last time the data was given to you.
Depending on how the data is aggregated, subtotals can change over time. Project Attributes such as service, sector, industry or studio can change.
9. What kind of revenue do you want? Gross? Fee?
Going back to question 1, if the request is external, maybe we want to use the larger number.
10. Are there any projects we should exclude? Highlight?
Make sure that you aren't including system level projects, or projects that may have write off's.
11. Are there any privacy issues with providing this data?
Does the data expose a confidential project or relationship with a client?
12. When is the data needed by you? When is the data needed for your deadline?
Hitting the first deadline allows some back and forth between the others involved so that you meet the end deadline.
