Scheduling the backup operations should be one of the elements that are imperative in the work of any DBA.
This simple action will save you lots of time and effort in the future. Scheduling backups can be done through the visual interface of SQL Server Management Studio (SSMS) as we will see next.
Doing backups might become a repetitive and reflex action if done for quite a long time. But due to this, you might skip a few things at the beginning and never add them to your checklist schedule when doing backups.
The following article presents a list of databases to backup and reasons why you should do it.
This article shows three ways of how to move your data from SQL Server table or query to Excel or CSV file.
You’ve recently come across a peculiar type of file with a .bak extension, and you know you are supposed to restore it in order to get the data./p>
This article will show you what to do in case you have such a file, and you need to open it to access the information.
If you encounter the error message, “the media family on device is incorrectly formed. SQL Server cannot process this media family,” you may not initially understand exactly what happened.
This post will try to give you a few suggestions as to what might have gone wrong and what to do in those situations.
If you’re here, then there’s a high chance you already know the importance of good backups and what they mean to a serious business.
Taking care of database backups is an important and very sensitive job.
This is why we tried to make a shortlist of some backup best practices that you should be aware of when you’re either doing backups or you’re trying to restore them, in order to be covered for any of the common and slightly uncommon situations involving backups.
SQL Server has such a thing as transaction log tail backup. In this article, we will figure out what it is, why it is needed, and how to do it.
In this article, we will offer information about tail-log backups, a feature that is available for SQL Server versions 2005 and newer. This is a topic which you should be aware of if your backup and restore process for your SQL Server databases is using either the FULL or Bulk-Logged recovery model.
This post will address the issue of backing up the Transaction Log in the unfortunate eventuality when your SQL Server Database is damaged.
We will offer details regarding how you can do your Transaction Log backup with either T-SQL queries or by using the graphical interface of SSMS (SQL Server Management Studio) in a step-by-step example.
Now that we have previously discussed about backup compression, it is time we offer details about how to configure compression for your backups.
Just as a short reminder, backup compression is a powerful feature offered by SQL Server (versions 2008 and newer) that allows you to shrink the amount of storage space used by your backup files while at the same time increasing the speed of recovery, which goes hand in hand with lower CPU usage when restoring the database from your backup.
