As a DBA, your first week at a new environment can be testing to say the least. Worst case scenario is that you arrive in an environment where there is no SOP (Standard Operating Procedure), best practice is unheard of, the databases are running themselves (maybe in fantasy land), and they have no idea why you were hired. If all the mentioned are true, then all I can say is RUN! We are DBAs, not Magicians, although that depends on whom you ask.
The first couple weeks are challenging if you are not prepared, but if you come prepared then it should be a not-so-rough transition. When you come to a new environment, after meeting with the storage team, sysadmin team, and other important departments, you can finally find out what you are working with. To list off some of the main things you need to know or find out:
- Naming convention of Production, Test/QA, DEV environment
- When and WHERE are backups
- What kind of backups
- Disaster Recovery?
- Total servers/databases
- Jobs (indexes?)
- SLAs (Service level agreement, this would be nice to know if possible)
- Drives (to make sure tempdb and backups are not on the same drive)
- Is there an MSX server?
- When you get paid (Come on we all think it)
Now it is understandable that every environment is different in some way, shape or form, but the above list is pretty standard across the board. I know I am not the only one that likes to keep some generic scripts handy for just in case. If I am ever in such a position, below is a quick example of the script I would use.
Script to get Jobs info:
SELECT name AS job_name, Suser_Sname(owner_sid), job_id, date_created, datediff (dd, date_created, date_modified) AS Days_since_last_modification, Enabled = CASE WHEN Enabled = 0 THEN ‘Disabled’
ORDER BY name