Indexes and Statistics with Always Encrypted
In this short post we look at the ability to be able to have (or not) indexes on columns encrypted using Always Encrypted.
2023-06-20
131 reads
In this short post we look at the ability to be able to have (or not) indexes on columns encrypted using Always Encrypted.
2023-06-20
131 reads
If you under promise and overdeliver then you will always have happy clients.
2023-06-19
26 reads
Here we look at a common query "anti-pattern" that can create performance problems - and how you work around it.
2023-06-14
401 reads
Introduced with SQL 2016, Query Store was, probably without doubt, the most anticipated and talked out new feature. In this post we'll just take a brief look at it,...
2023-06-14 (first published: 2023-05-31)
625 reads
In this post we’ll look at how you interact with data that is encrypted using Always Encrypted. The examples here will show how you run queries from SSMS, in...
2023-06-13
37 reads
In SQL Server you can also compress your encrypted backups. Unlike TDE this has been possible with Backup Encryption since the feature was first made available, and there have...
2023-06-12 (first published: 2023-05-24)
358 reads
There is a scenario I have seen again and again. A company has developed a nice piece of software which many clients are running with happily. Then along comes...
2023-06-12
18 reads
Script to identify the most expensive queries on your database server using the Query Store DMVs. This allows you to look at data from a specific time frame, as...
2023-06-07
323 reads
In this post we're going to go through the steps to set up Always Encrypted and create an encrypted column. As with my last post we're looking at the...
2023-06-06
33 reads
Unlike TDE, there is some extra CPU overhead when you take an encrypted backup as the data has to be encrypted before being written to disk – whereas with...
2023-06-05 (first published: 2023-05-22)
266 reads
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers