Transparent Data Encryption (TDE)

External Article

How to Move a TDE Encryption Key to Another SQL Server Instance

  • Article

If you have a database backup of a Transparent Data Encryption (TDE) enabled database, the database backup will contain encrypted data. Because the database backup contains encrypted data you can’t just restore it to any instance. You can only restore the database backup to an instance that contains the same certificate used to originally encrypt the database.

2018-02-20

2,970 reads

External Article

Encrypting SQL Server: Transparent Data Encryption (TDE)

  • Article

Transparent Data Encryption (TDE) encrypts the data within the physical files of the database, the 'data at rest'. Without the original encryption certificate and master key, the data cannot be read when the drive is accessed or the physical media is stolen. The data in unencrypted data files can be read by restoring the files to another server. TDE requires planning but can be implemented without changing the database. Robert Sheldon explains how to implement TDE.

2017-03-24

5,410 reads

Blogs

SQL Server 2025 GAs Today

By

If you aren’t watching the Ignite keynotes today, then you might have missed the...

Run SQL Server 2025 and SQL Server Management Studio on macOS Tahoe

By

Short version You want to get this running as fast as possible. Do these...

The Roundup for T-SQL Tuesday #192

By

Last week I asked you to write about SQL Server 2025 and what things...

Read the latest Blogs

Forums

Best way to log Data Flow errors in SSIS 2005?

By jakestopher

Hi everyone, I’m working with some old SSIS 2005 packages, and I’m trying to...

Advanced Excel Mastery for Finance, Accounting & Payroll – 2025 Edition

By jackraines1717

Unlock the full potential of spreadsheets with our “Advanced Excel Mastery” course tailored for...

2025 Form 1099 Reporting Requirements: Essential 1099 NEC Updates

By jackraines1717

Prepare your team for the upcoming compliance shift with our “2025 Form 1099 Reporting...

Visit the forum

Question of the Day

Specifying the Collation

I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:

DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'

SELECT  p.PersonType,
        p.Title,
        p.LastName,
        c.CustomerID,
        c.AccountNumber
 FROM Person.Person AS p
 INNER JOIN Sales.Customer AS c
 ON c.PersonID = p.BusinessEntityID
 COLLATE @c
Will this solve my problem?

See possible answers