For any SQL Server DBA who’s been in the field for a long time, you know that the exercise of restoring backups taken in SQL Server 2000 (and even SQL Server 2005 without using the CHECKSUM option) was many times a sweat-filled lottery. You usually gambled and/ or prayed to your respective deity that your backups would actually work. Why? Because you knew that restore failures were all too common. Despite SQL Server’s assurance that all was well because you had already verified your backups with the RESTORE VERIFYONLY option. So why was this the case? Why did restore operations fail so frequently? Let’s delve a bit more into the innards of the RESTORE VERIFYONLY and CHECKSUM options to find out.
Sometimes it helps to have simple access to detailed information about your latest backups. This is why a backup report always comes in handy when you need to know when was the last time your database or a specific database was backed up and what was the last type of backup that was taken. In order to help you with this we’ve composed a small script which you can easily run to find out important information.
It’s important to have flexibility and not sacrifice security when backing up your databases. For this reason, some DBAs will prefer to backup to UNC paths on their local network. This will keep the backups in a closed environment with access only to those users inside the network which are authorized. In this article we will show you how to backup to UNC paths in the simplest way possible, by using SQLBackupAndFTP, instead of using complex and confusing T-SQL and complex maintenance plans.
One of the most important operations and tasks that need to be performed on a database is the backup process. In this sense, you can prompt to backup a SQL Server database from the command line using SQLBackupAndFTP with some additional parameters, which are also passed in the command terminal. More…
Backing up your database is one of the most important tasks a DBA should have set. There are multiple options in terms of backing up a database, for instance you could backup a SQL Server database to NAS drives. If you prefer this option or if your organization requires you that you backup your databases on your local network then you can count on SQLBackupAndFTP to assist you with this and make the job much easier! More…
One of the most often made assumptions is that if you have made a backup of your database, your data is safe. Unfortunately, this is not true, and I’ll explain why, but don’t forget to verify SQL Server backup files after backup! SQLBackupAndFTP allows you to do this, in order to be absolutely sure that indeed, your data is safe!
SQL Server maintenance is just as important as creating backups of your databases. Without a doubt there are a lot of organizations that install a SQL Server database or more without setting their maintenance plans up first Things generally go smoothly and at the beginning there is no problem, that is, until a problem appears. More…
SQL Server backup email notification to let you know if your task has succesfully finished or not? Read this article to find out how to do this, really easy with the help of SQLBackupAndFTP