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 […]
2019-05-30
479 reads
2017-09-28
827 reads
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
2016-12-22
891 reads
2015-12-09
1,243 reads
2015-07-13
1,845 reads
Running AI and data pipelines on the edge instead of the cloud has gone...
By Steve Jones
While writing another post I realized my UNION query didn’t work as one might...
By James Serra
Since the release of my book Deciphering Data Architectures: Choosing Between a Modern Data...
Comments posted to this topic are about the item Secure Cached Plans
Comments posted to this topic are about the item Complex Data Processing with dbt...
Comments posted to this topic are about the item Over or Under Provisioned
The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?
See possible answers