First day on the job as a DBA

So I’m starting out a new job today and figured I would write up a checklist of things I needed to complete to own the Databases I have to start managing.

  1.  Get a list of Servers I’ll be managing/owning.  This can be done with a script or just by the company letting you know which ones.  It’s not a bad idea using the script to find some other servers that might be out there that the company was not aware of.  Pinal Dave has a good example of this on his blog.
  2. Run the SP_Blitz script from Brent Ozar (blog | Twitter) this is full of all sorts of good tidbits on what you need to look at for a server.  Check out the blog post in the link above and it will fill you in on the many great things this script can do for you.
  3. Get a DBA database created on each server.  I typically use this to house all sorts of maintenance type things and monitoring and alerting.  Every DBA should have a DB to call their own.
  4. Create the server side trace.  Years ago back in SQL 2000 I wrote a server side profiler trace that would run all the time and store the contents down to a table that I could later review to watch performance of queries hitting the DB.  Over the year’s fellow DBA’s have made updates to the script and made it better and it’s one of those key things I still depend on now.  I should get a future blog post out on this one.
  5. Create perfmon counters.  I store perfmon counters down to a db through an odbc connection in perfmon.  This way I can use a custom set of reports I’ve created to report trends on my server/db performance.  This also gets me started on my benchmark and knowing where things are when I started.  I should have some future blogs on this.
  6.  Install SSMS tools pack.  No one should go without this tool.   Saved me more times than I can count I would suggest it to everyone.
  7. Check the backups/backup schedule.  Blitz script is going to tell me some of this but I want to make a point to check with the business as to what the backups schedule is and make sure that matches what is really happening.
  8. Check the security model and who has access to the DB.  Again Blitz script might tell me some of this but I’ll make it a point to make sure something like domain admins don’t have full rights to the db and there are 100 people in domain admins (yes I’ve seen this before).

This is all the primary things I could come up with on day 1.  There’s still more items I’m sure but these are key and all have to be in place so I can continue moving forward from here I should have a good base to work with.

If you have other suggestions  let me know!

Advertisements

2 responses to “First day on the job as a DBA

  1. I would add “get a list of application owners” and “meet primary infrastructure contacts (server/storage/etc.)” to the list – but maybe that’s day two. {-:

    Good list!

  2. Pingback: DBA Week 2 A follow up to your first day. | Sql Server Insane Asylum (A Blog by Pat Wright)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s