Things That Drive a DBA Crazy When Starting a New Job

, 2018-12-07 (first published: )

In the past 5 months I have started two different jobs, so that leaves it up in the air as to which job or jobs (plus a previous job did some of these) are practicing these bad habits but these are the top 10 things that drive DBAs crazy when they start new jobs.  Keep in mind the company had never had never had a DBA before but still come on there are too many free resources out there for accidental DBAs and they had written plenty of stored procedures.

  1. Everyone can guess this one. Go ahead try before you read it.  Everyone is a you guessed it a sysadmin.  There is just way to many things that can go wrong from drop databases to settings being changed to inconsistent things being setup that the DBA doesn’t know about after they have fixed up the server.
  2. Production databases having a SLA but no recovery strategy, i.e. databases in SIMPLE mode so no log backups, but then test databases in FULL mode.  Just why?
  3. Having test databases on the same server as your production databases.  Why when you have the resources to create test servers.
  4. Running a server without enough memory, seriously a 300 GB database (not to mention the other databases on the server competing for that buffer pool) trying to run in under 64 GBs is usually going to be slow and you have the resources to give it max standard edition will take at 128 GBs and you have it configured to use a minimum of 80 GBs anyways.
  5. Having compatibility modes set all the way back to SQL Server 2008, hey we are running 2016.  Let’s use the new cardinality estimator.
  6. All the database files on one drive, let alone on the C drive where snapshot backups are taken quite frequently freezing IO.
  7. Oh, and can we have SQL Agent Alerts please, how did you know there was something wrong with the server before?
  8. Having databases with 10,000+ DTA indexes yes you read that number correctly, I saved over 400 GBs removing the include columns from them.  And oh got rid of the DTA statistics.
  9. Still not have your Power Plan set to High Performance.
  10. Lastly not having complete maintenance plans, like only having backups or not backups or only backups and nothing else, or even setting up everything including Shrink Database.  Please don’t use those go use Ola’s scripts.
  11. Bonus one no patches having ever been installed on the operating system or SQL Server in years.

Any company without a DBA or any new DBA look at Brent Ozar’s 6-month Training Plan , it’s free.

If you had any things that have driven you crazy when starting a new job leave them in the comments, I’m curious I may need to check them out.

Rate

Share

Share

Rate

Related content

Database Mirroring FAQ: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup?

Question: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? This question was sent to me via email. My reply follows. Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? Databases to be mirrored are currently running on 2005 SQL instances but will be upgraded to 2008 SQL in the near future.

2009-02-23

1,567 reads

Networking - Part 4

You may want to read Part 1 , Part 2 , and Part 3 before continuing. This time around I'd like to talk about social networking. We'll start with social networking. Facebook, MySpace, and Twitter are all good examples of using technology to let...

2009-02-17

1,530 reads

Speaking at Community Events - More Thoughts

Last week I posted Speaking at Community Events - Time to Raise the Bar?, a first cut at talking about to what degree we should require experience for speakers at events like SQLSaturday as well as when it might be appropriate to add additional focus/limitations on the presentations that are accepted. I've got a few more thoughts on the topic this week, and I look forward to your comments.

2009-02-13

360 reads