Having a complete backup history of all of your backup and restore operations can become quite useful at times.
All the data that you might need to be related to this, like who created the backup, at what time, on what media, and many other details are stored in the system databases of the SQL Server instance.
So, SQL Server 2014 CTP2 has been released and now we can have a look at some of its new features before its official commercial release later this year.
What we’re mostly interested in is, obviously, improvements related to backups and restores. Here is a shortlist with improvements.
At the time this article was written only SQL Server 2014 CTP2 was available, so information related to this subject is limited to only what was known from the perspective of the CTP2 edition.
This post is a continuation of a previous post where we explained how to do a maintenance plan that will take care of creating backups via a schedule.
Now that we have a schedule that consistently creates backups, we might want to create a backup cleanup schedule to remove older backup files.
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.
We already know that backups are important for securing your databases from data loss.