Always Encrypted

SQLServerCentral Editorial

High Prices for High Security

  • Editorial

I was excited to see the new Secure Enclave technology come to Always Encrypted (AE) in SQL Server 2019. I've thought that the way Microsoft implemented the AE technology in SQL Server 2016 was a start and a good step forward, but it had too many restrictions. Kind of like Availability Groups in 2012 and […]

You rated this post out of 5. Change rating

2019-05-30

456 reads

External Article

SQL Server Encryption: Always Encrypted

  • Article

Is 'Always Encrypted' SQL Server 2016's most widely important new feature? It is significant that 'Always Encrypted' in SQL Server is in all editions of SQL Server. Because of the increasing importance of encryption to data governance, it allows encryption for the sensitive application data for everywhere beyond the application's client connection, including network, server, database and storage. Robert Sheldon explains what it is, why you should try it out, and how to set about it.

2017-04-10

4,486 reads

Blogs

Fabric as a Data Mesh Enabler: Rethinking Enterprise Data Distribution

By

For decades, enterprises have approached data management with the same mindset as someone stuffing...

Truncate Table Pitfalls

By

 Truncate Table Pitfalls Truncating a table can be gloriously fast—and spectacularly dangerous when used carelessly....

dataMinds Connect 2025 – Slides & Scripts

By

You can find all the session materials for the presentation “Indexing for Dummies” that...

Read the latest Blogs

Forums

Technological Dinosaurs or Social Dinosaurs?

By Grant Fritchey

Comments posted to this topic are about the item Technological Dinosaurs or Social Dinosaurs?

DBCC CHECKIDENT

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKIDENT

Distributed Availability Group Health: T-SQL and Zabbix

By Pablo Echeverria

Comments posted to this topic are about the item Distributed Availability Group Health: T-SQL...

Visit the forum

Question of the Day

DBCC CHECKIDENT

What is returned as a result set when I run this command without a new seed value?

See possible answers