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.
If you have limited access to SQL Server’s file system, getting the .bak file back may be an issue. In this case, you can send database backup to some network folder if both you and the SQL Server have access to it.
We will show how to do it with SQLBackupAndFTP. Continue reading How to backup SQL Server to UNC Path
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. Continue reading How to perform SQL Server maintenance