Hot answers tagged

1

SQLmojoe has good points in the answer. 2 things that you need to consider : The cert that you used when taking backup should be preserved as is. The cert should not be changed or renewed (even if it is expired). Renewing the cert will change the cert thumbprint and you wont be able to restore the database backup. The user account should have VIEW ...


1

Assuming you have the process down tight (as in scripted, tested, re-tested, and tested with the newest and most junior persons on the team) the only other area that I seen people slip on is accessibility of the key. Most people get that they should not store it in the same place as the backup files or even transport them together. What is sometimes missed ...


1

With security in SQL Server, one needs to be very watchful that permissions are not indirectly granted when not intended. Designing granular permissions for the SQL Server system must be a very meticulous task for Microsoft. Once created, the certificate can be altered, but only to drop the private key. View definition lets the user see the metadata, however ...


1

If you want to restore on a different server, you should be able to do so with the certificate, private key and database backup file(s). When a certificate is created in any database in SQL Server, it is part of an encryption hierarchy. The certificate itself only contains a public key, which needs no protection, however, the database will also contain a ...



Only top voted, non community-wiki answers of a minimum length are eligible