DBA Best Practices?

What are the things that you do, or want to do, on a daily basis to manage your database infrastructure? This blog entry is going to be a little different than my regular entries. I’m going to use it as an open-ended introduction to encourage readers to post their favorite best practices. Give the following questions some thought and if you’ve got something to share, post a comment on it below.

What things have you found to be most helpful to automate in administering your databases? Yes, I know that all the DBMS vendors are saying that they’ve created the “on demand” “lights-out” “24×7” database environment, but we all know that ain’t so! So what have you done to automate (either using DBMS features or scripts) to keep an eye on things?

How have you ensured the recovery of your databases in the case of problems? Application problems? Against improper data entry or bad transactions? Disaster situations? And have you tested your disaster recovery plans? If so, how? And were they successful? Do you set RTOs (recovery time objectives) to ensure that your backup plan is appropriate?

What type of auditing is done on your databases to track who has done what to what data? Do you audit all changes? To all applications, or just certain ones? If only certain ones, is it to support regulatory compliance or some other reasons? Do you audit access, as well as modification? If so how? And do you audit everything done by privileged users like DBAs and SysAdmins?

How do you manage change? Are database schema changes integrated with application changes? If so, how? If not, how do you coordinate things to keep the application synchronized with the databases?

What about patch management? How do you determine when to apply DBMS fix packs and patches? And then manage which servers have been patched and which have not?

Is your performance management set up with triggers and thresholds and then farmed out to DBAs by exception or is it all reactive, with tuning tasks being done based on who complains the loudest?

When do you reorganize your data structures? On a pre-scheduled regular basis or based on database statistics? Or a combination of both? And how do you determine which are done using which method? Do you regularly reorganize both table spaces and indexes?

Do you EXPLAIN every SQL statement before it goes into production? Does someone review the acess plans or are they just there to be reviewed in case of production performance problems?

Does your chewing gum lose its flavor on the bedpost overnight? (Just checking to see if you are still paying attention to these questions.)

How is security managed? Do the DBAs do all of the GRANTs and REVOKEs or is that job shared by security administrators? Are database logons coordinated across different DBMSs? Or could I have an operating system userid that is different from my SQL Server logon that is different than my Oracle logon — with no capability of identifying that the user is the same user across the platforms?

Any other questions I should have asked?


About craig@craigsmullins.com

I'm a strategist, researcher, and consultant with nearly three decades of experience in all facets of database systems development.
This entry was posted in Database security, DBA, performance, tools. Bookmark the permalink.

3 Responses to DBA Best Practices?

  1. Accommodation Whyalla says:

    A colleague recommended me to your website. Thanks for the details.

    IN SQL SHOWCASE – How do you write the expession/systex?

  3. field gate says:

    cool. thanks for the article good write up

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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s