My name is Aamir Syed and I run SQLEvo. I optimize the speed, efficiency, and stability of SQL Server. When not working I like to lift weights, play music, and travel with my wife.
It's becoming less surprising, but no less scary when I find shops not taking regular database backups. This happens quite often in situations where there is no dedicated DBA. Meaning someone else just kind of took over those responsibilities ("accidental DBA", if you will). Why can't I just include the .mdf and .ldf files in a system wide backup? Some of the common explanations I get is that "Well we run a file system backup, so the database files are backed up". Unfortunat
If you're storing any of your database backups off site or in the cloud, you might want to look into encrypting your backups. This feature was first introduced in SQL 2014. Since we're working with encryption on SQL server the first step is to create a Database Master key. Then we create a certificate. Then run your backups with the correct syntax and specify the algorithm you'd like to use (AES 256,128, 192 or Triple_DES_3Key). #sqlserver #backups #DBA #Encryption
