The folks on Twitter liked this, so sharing it here:
It’s a one-slide summary from a SQL Critical Care client’s deck, so obviously it’s abridged, but I think it does a pretty good job of summing things up.
Some highlights of the conversation:
A solid 20 minutes of my talk from last year’s Summit, summed in one slide. Well, done, @BrentO! Could be simplified further to: TDE – what you do for compliance but not actual security, and Always Encrypted – what you do for actual security but not compliance
— Daniel Mallott (@DanielMallott) July 30, 2020
I have always thought of TDE as a chocolate fire guard. When the fire is going (database online) and someone hasn’t secured the database properly TDE is worthless. Sure TDE stops file theft (lower risk). I would include anyone with read access on protect list
— Kevin Lewis (@Kevin_S_Lewis) July 30, 2020
That’s it. That’s the post. If you want more words and pictures, follow @BrentO on Twitter.
This week's sponsor: Free eBook: Learn from SQL Server experts Brent Ozar, Janis Griffin, and Pinal Dave as they share their top tips for performing tuning.