Try detaching and re-attaching the database files to a different SQL Server instance and you can easily do so. But with backup encryption, only the backups are secured. That also means that, whether you use TDE or backup encryption, your database backups will be encrypted. So, What’s The Real Difference?īoth TDE and backup encryption provides encryption – the former encrypting the MDF/NDF and LDF files together with the backups taken, the latter just the backups. ![]() ![]() I wrote an article back in 2008 about how we can implement transparent data encryption to provide encryption at rest as well as for the backups we take on the databases. When customers have Enterprise Edition, my default recommendation is to use transparent data encryption. ![]() I’ve worked with customers in the past who had to use encryption utilities like TrueCrypt and GnuPG to encrypt their backups because they do not have Enterprise Edition. Since transparent data encryption has been available since SQL Server 2008, why would I still need the backup encryption feature?įor one, transparent data encryption is an Enterprise Edition-only feature whereas backup encryption exists in Standard Edition (I can stop right here and move on to the next topic of discussion.) The price tag of an Enterprise Edition license is more than enough justification to consider using backup encryption. This particular question came up while I was delivering a workshop last week on the new features in SQL Server 2014.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |