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 which 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.
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.
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.
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.