The way you set the expiration date on a backup for SQL Server databases is quite easy.
You have two options for doing this. In order to find out, read the following article where we will show you both options.
So, in our previous articles, we introduced you to what is SQL, for what it is used, how it stores data in databases and tables, and how it works through commands (SQL query), and how the commands are different based on what SQL type you use.
Now that we have the overview, we are going to dive into writing our first SQL command, which in technical terms is called a query, as you might already know.
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.