DBA is a demanding job. Expertise is required at different levels – hardware, OS , Database Server and Application Layer. As pressure increases to give input at an operations and architecture level, remember the two primary tasks of the DBA is to maintain availability and performance.

These are common mistakes made by all DBAs at one point , and are a selection I’ve spotted in the last couple of weeks. The aim is to improve , and set up procedures where you can minimise these mistakes.

 Bad memory management

Operating System runs into trouble if memory is not managed with MIN and MAX. Also look at different configuration for 32 bit and 64 bit architecture.SQL Server memory configuration management  is critical

Not creating a Database Disk IO profile

Don’t just place all databases on the same drive , hoping for the best! Make decisions of database placement based on the database disk IO profile

Auto Shrink Enabled

In DBA community this message is like a mantra- and yet so many DBAs do not follow this advice. Auto Shrink Enabled is  not managed . Causes fragmentation

 Bulk Imports at Production Peak Times

Causes performance issues during peak production times.  Don’t do it unless absolutely necessary.

Not defining a Backup Strategy and ensuring Backups occur

Many DBA mistakes can be forgiven. Not this one! Consider a SQL Server backup review with Powershell

Not monitoring database servers

Don’t wait for users to start shouting, fix the problems as soon as possible.

No Performance Tuning

Don’t just verify backups and do patch upgrades- provide proper feedback to the developers and application owners. Expand your knowledge of the server and applications running on them.What is SQL Server Query Tuning?

 Not enough automation

Develop an automation psychology . Anything that is repeatable , think of automating. Spend your time productively.

Allowing poor SQL code onto a Production System

Allowing developers to execute poor  sql code  causes serious performance issues. If  resources are inadequate to check before going live- at least  monitor on Production Server and feedback to developers

Everyone using one login account

You might as well pack up and go home! If everyone uses the same account and it has elevated privileges – you’re asking for trouble! Make sure security follows the security policy

Let me know what you think and add your DBA mistakes into the comments. I view this as a learning experience. It is a challenge for the DBA to maintain availability and performance – especially in a 24 x 7 environment  .