These are notes taken from the Houston SQL Pass User group from July. This presentation was given by John Cook, (Data Platform Solution Architect Microsoft) who did a great job with limited time on providing some great details on the new functionality with SQL 2016. To follow him, take a look at sqlblog.com where he posts or follow him on twitter. Thanks to him for the overview.
Microsoft Data Platform specialist and Registered Nurse
#### John Paul Cook
SQL Blog - Blogs about SQL Server, T-SQL, CLR, Service Broker, Integration Services, Reporting, Analysis Services, Business Intelligence, XML, SQL Scripts, best practices, database development, database administration, and programming
Most of the new features included in 2016 have been tested in the cloud. They are implementing cloud-first with features. Therefore, most on prem features have been throughly tested in the new world, sometimes even up to months.
dynamic data masking
- If you know a specific value you could get the results back in a specific query by putting in where clause. This would retrieve the row masked, but you still knew the results due to this “brute force attack”. Dealing with security means you’d prevent adhoc queries anyway. You want to ensure that that scenario doesn’t happen.
- This would be categorized more as obfuscation. This is not the same as encryption.
- New grant permission for UNMASK
- Encryption at column level
- Deterministic: need this for being able to search/join among different tables
- Random: Good for increasing the difficulty of breaking the encryption.
- Encryption increases to the size of the data, taking up more size
- Has some limitations on Collation. The example was COLLATE Latin_General_BIN2
- This is offloaded to the client which converts the value with ado.net 4.6.1. This means a certain compatibility would need to be maintained to use this with legacy applications. This is done on the client. Unless you give the key to the dba, they can’t see the information.
- Additional connection string value is required, per SSMS has to convert and interpret this value.
column encryption setting=enabled
Stretch is more “stretch table” to Azure. This means you’d bind a function to your sql server with the logic to archive. This would let you store very cold data without having to maintain locally. Another positive to this is that each table is contained as it’s own “database” in Azure. They maintain the backups for you, so your backup windows are not impacted. You only have to backup the local data.
Microsoft keeps track of all your changes in a table. You have to enable on each table individually. This functionality stores the history of all changes to ensure this history is tracked. This used to require a lot of coding.