All New Collations in SQL Server 2017 Implicitly Support Supplementary Characters

SQL Server 2017 adds 68 new Collations, but none end with "_SC". This seems to be due to Supplementary Characters being supported by default (which is great šŸ˜ŗ).

SQLCLR vs. SQL Server 2017, Part 6: ā€œTrusted Assembliesā€ ā€“ Whitelisted Assemblies can’t do Module Signing

"Trusted Assemblies", a new feature starting in SQL Server 2017, is a means of whitelisting Assemblies that one feels pose no threat, and can be created (and used) without needing to be a) signed and b) have a corresponding signature-based Login that has been granted the UNSAFE ASSEMBLY permission. In Part 4 of this series… Continue reading SQLCLR vs. SQL Server 2017, Part 6: ā€œTrusted Assembliesā€ ā€“ Whitelisted Assemblies can’t do Module Signing

SQLCLR vs. SQL Server 2017, Part 5: ā€œTrusted Assembliesā€ – Valid Use Cases?

In the previous post in this series on SQLCLR in SQL Server 2017 ā€” Part 4: ā€œTrusted Assembliesā€ ā€“ The Disappointment ā€” we looked at what the "Trusted Assemblies" feature is, what it meant to do, the problems with it, and what the better and more appropriate approach is. "Trusted Assemblies" is a simple mechanism… Continue reading SQLCLR vs. SQL Server 2017, Part 5: ā€œTrusted Assembliesā€ – Valid Use Cases?

SQLCLR vs. SQL Server 2017, Part 4: ā€œTrusted Assembliesā€ – The Disappointment

"Trusted Assemblies", introduced in RC1 of SQL Server 2017, seems like a reasonable fix for one, if not two, problems resulting from the new "CLR strict security" setting. But are there any problems with it? And even if not (don't worry, there are), might there be a better approach? Perhaps something simple that was overlooked?

SQLCLR vs. SQL Server 2017, Part 3: “CLR strict security” – Solution 2

Welcome back, everyone. In the previous post in this series, I explained how to work within the new SQLCLR security restriction in SQL Server 2017 (i.e. that all Assemblies need to be signed and have a corresponding Login that has been granted the UNSAFE ASSEMBLY permission). That approach is 22 steps, but they are all… Continue reading SQLCLR vs. SQL Server 2017, Part 3: “CLR strict security” – Solution 2

SQLCLR vs. SQL Server 2017, Part 2: “CLR strict security” – Solution 1

As mentioned in Part 1 of this "SQLCLR vs. SQL Server 2017" series, the new clr strict security server-level configuration option requires that in order to create any Assembly, even a SAFE one, it must be signed (by a Certificate or Strong Name Key), and there must already exist a corresponding Login, based on the… Continue reading SQLCLR vs. SQL Server 2017, Part 2: “CLR strict security” – Solution 1

SQLCLR vs. SQL Server 2017, Part 1: “CLR strict security” – The Problem

The Good, the Bad, and the UgleĢ…eĢ… (need to avoid copyright infringement šŸ˜‰ ) SQL Server 2017 is soon to be officially released (i.e. RTM) and there are some impressive changes, with some being impressively good, and some being impressively bad. The Good Some amazingly good changes are: Linux as a platform (see my editorial… Continue reading SQLCLR vs. SQL Server 2017, Part 1: “CLR strict security” – The Problem