2018-03-06
885 reads
2018-03-06
885 reads
By default, SQL Server does not encrypt data in a SQL Server database in an encrypted format. When SQL Server 2008 was introduced, Microsoft implemented Transparent Data Encryption (TDE). When TDE is enabled on a database SQL Server will encrypt the database as data is written to the disk.
2018-02-28
2,572 reads
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
Simon Liew explains how to generate a new TDE certificate to replace the previous, and also looks at the steps needed if the database is in an Availability Group.
2018-02-13
2,865 reads
2017-04-27
888 reads
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
2017-03-06
994 reads
2017-02-24
1,054 reads
Aaron Bertrand (@AaronBertrand) revisits the impact that eliminating DONE_IN_PROC messages using SET NOCOUNT ON may or may not have on query performance
2016-03-07
5,657 reads
There are several ways to implement encryption in SQL Server; Arshad Ali focuses on Transparent Data Encryption (TDE), which was introduced in SQL Server 2008 and is available in later releases.
2014-05-28
3,280 reads
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Short version You want to get this running as fast as possible. Do these...
By Steve Jones
Last week I asked you to write about SQL Server 2025 and what things...
Hi everyone, I’m working with some old SSIS 2005 packages, and I’m trying to...
Unlock the full potential of spreadsheets with our “Advanced Excel Mastery” course tailored for...
Prepare your team for the upcoming compliance shift with our “2025 Form 1099 Reporting...
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