When backing up your SQL Server database, you have the option of taking transaction log backups. These are quick, small backups containing a sequence of all your database’s changes. Transaction log backups are mightily useful for point-in-time recovery.
It goes without saying that as a DBA, one of your most important tasks is to schedule and ensure regular backups of your databases. But by ‘databases’ here, we usually mean your user-created databases. But SQL Server also automatically creates and maintains a number of system databases. So should you also back these up? Well, the answer isn’t a simple yes or no …
If you’re looking for an easy way to quickly restore a database backup then you have found the right place.
Take a look at the article below to find out how you can achieve this.
Surely if you have arrived here you are facing this problem and looking for a solution. Well, you have come to the right place. In the article below we will show you how you can achieve this.
SqlBak’s dashboard has been upgraded to be a more user-intuitive interface, in order to provide the most essential information in just a quick glance as well as make modifications to the job.
It’s still very easy to create backups, to schedule them, to set custom backup destinations, and of course, all of the other features you will need to make sure your backup process is up to the highest standard. Let’s have a look!
We will also explain what are some of the most advanced options for backing up databases and how you can give these privileges as well to some of your most trusted users.
If you can connect to your database, you can run this query and find out when was the last time your databases were backed up
and when were the last times a Full, Differential, or Transaction Log backup was taken.
But what do you do when you do not have remote access to your databases, but still like to have a quick review of your last successful backups? Well, we’ll cover this too…
Encountering a “Cannot perform a differential backup for database, because a current database backup does not exist” error might generate some confusion if you look into your backup log and can see that FULL backups have been successfully created.
This article will try to give you an answer as to why this happens and a solution, that will hopefully be applicable to your situation.