Impact of implementing Transparent Data Encryption on SQL Server 2008 database and related objects

  • We have been asked to investigate the impact of using Transparent Data Encryption (TDE) on

    our SQL Server 2008 database environment

    Do you know what could be the potential impact on our SQL Server Reports, SSIS, SQL Server Agent jobs,

    strored procedure, function code, if we apply TDE to our databases? Would code have to be re-written?

    In particular, we are looking at the following area of concern:

    o SQL Server Reporting Services (SSRS)

    o SQL Server Integration Services (SSIS)

    o SQL Server Agent Jobs

    o Database Security – User and SQL Server roles

    o Backups – Software used to backup SQL Databases , not using T-SQL commands

  • As this feature's name implies it is completely transparent to the clients, so no code would have to be rewritten. The things that you do have to be aware of are:

    1) You'll might see an increase in the CPU usage because the server will have to encrypt anything that it writes to disk and decrypt anything that it reads from disk and writes to the memory.

    2) Most important - Keep the certificate and the password that is needed for the restore operation in a very safe place. If you'll lose it, you won't be able to use the backups and you will loose all the data.

    Adi

    --------------------------------------------------------------
    To know how to ask questions and increase the chances of getting asnwers:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • Adi Cohn-120898 (12/1/2016)


    As this feature's name implies it is completely transparent to the clients, so no code would have to be rewritten. The things that you do have to be aware of are:

    1) You'll might see an increase in the CPU usage because the server will have to encrypt anything that it writes to disk and decrypt anything that it reads from disk and writes to the memory.

    2) Most important - Keep the certificate and the password that is needed for the restore operation in a very safe place. If you'll lose it, you won't be able to use the backups and you will loose all the data.

    Adi

    Hi Adi

    Thanks for that.its very useful. So really code doesn't have to be re-written and our SSRS reports and SQL Server Agent jobs are unaffected?

    Also we use Redgate Data Compare 11 to synchronise databases. Would Redgate Data Compare be affected by TDE?

  • Nothing will be effected. TDE was designed to protect your data if someone get a hold on your database's files or backup files. TDE encrypts only the data in the files and decrypt it when it brings it into the memory. Since all the user processes read only data from memory and not from disk (and in case the data is not in memory another process is getting the data from the disk to the memory and only then our processes can read it), nothing has to be modified when you use TDE.

    Adi

    --------------------------------------------------------------
    To know how to ask questions and increase the chances of getting asnwers:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply