THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Argenis Fernandez

DBA Best Practices: A Blog Series

This blog has moved! You can find this content at the following new location:

Published Monday, November 12, 2012 9:11 PM by Argenis

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Dale said:

One of the issues that I've had is not that I have a good backup, and a good restore, it was that the data seemed correct, or non-corrupt, but there was no way to verify it was good and relevant data.

Looking forward to reading more.

November 13, 2012 1:12 AM

TedS said:

It depends!

The start to any backup strategy is a good long healthy discussion with the people who 'own' the data (DBA you protect the data, somebody else owns it)..

Their knee jerk reaction is that all data is scared and should have the best possible backup, but on deeper examination you can find ways to protect the data and minimize IO and CPU cycles.

Always a tightwire act isn't it!

November 13, 2012 9:48 AM

Karthik said:

It is very important that all the parties involved ( Business and Technical folks) know their RPO and RTO. Depending on that a suitable backup and restore strategy can be built.

November 13, 2012 12:29 PM

SQLFinn said:

One thing I personally consider important is an up to date documentation of your backup and restore processes. No matter how good the plans are, but they wont be much of a use if the procedures exists only in your head and someone else would need to perform the restore actions.

I also agree with previous comments, DBA's dont own the data and dont necessarily understand the business requirements or possible laws and regulations regarding the data. Good communication with the business/data owners is a must thing.

November 14, 2012 1:45 AM

jarry max said:

In my system now i want get more things for the work and now here a big things available for the all because now user have no need to take any problem for the work and here all things available for the user.

April 8, 2019 10:10 PM

Andrew Williams said:

Thanks for the useful article, I ve read a lot of stuff like

July 10, 2020 5:51 AM

MARTIN said:

What are the things that you do, or want to do, on a daily basis to manage your database infrastructure? This column is going to be a little different than usual … I’m going to use it as an open-ended introduction to the questions you need to answer in order to implement best practices for database administration. Give the following questions some thought and consider whether your organization has paid an appropriate amount of attention to each matter.

What are the practices and procedures that you have found to be most helpful to automate in administering your databases? Yes, I know that automation has been a standard claim for most DBMS vendors, as well as third-party DBA tool vendors, for many years. But are you really anywhere closer to an “on demand,” “lights-out,” “24/7” database environment yet?

So, what have you done to automate (either using DBMS features or scripts) to keep an eye on things? And, have you looked into how AI and machine learning might be able to assist with DBA chores?

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 from

And what about DevOps? If you want to bring your DBA practices into the modern era, you need to automate and integrate database application testing and change management to enable continuous delivery. If you do not have the tools in place to automate DBA procedures, implementing DevOps for database applications will be difficult to impossible.

July 18, 2020 9:21 PM

Sean Brither said:

Very entertaining post. I also want to recommend the service itself of fast and high-quality essays. A large number of satisfied customers for the work done.

November 17, 2020 9:37 PM

Leave a Comment

Privacy Statement