Glenn Berry talks about a few of the security features in SQL Server 2017 and reminds us to always test and validate the performance impact.
UPDATE November 17th, 2018 – Microsoft has pulled several patches for older versions of SQL Server. If you need TLS 1.2 support and can't move to a formally supported version, your recourse is to contact Microsoft support.
Recently I have been exploring Dynamic Data Masking, looking at ways that it can be used and I thought I would share my thoughts with you.
John Martin starts his security nuggets series, explaining why you should use encrypted connections for SQL Server if you take system security seriously.
In addition to StretchDB and AlwaysEncrypted, there are two more exciting features in the works for SQL Server 2016: dynamic data masking and row-level security. In the case of these two features, they'll be released first to the cloud platform (Azure SQL Database) and, later, to the on-premises version of SQL Server. READ MORE… Originally […]
Prior to SQL Server 2016, your main method for encrypting a SQL Server application was to use a feature called Transparent Data Encryption. TDE provides strong encryption, but with some shortcomings. First, you have to encrypt an entire database. No granularity is offered at a lower level, such as encrypting specific tables or certain data […]
There is a fix to address a remote code execution vulnerability for all supported SQL Server versions. @AaronBertrand shows which build you should install.