For SQLCLR in SQL Server 2017 and newer, when "CLR strict security" is enabled, does PERMISSION_SET matter, or are assemblies always UNSAFE?
(last updated: 2020-01-09 @ 13:15 EST / 2020-01-09 @ 18:15 UTC ) With the additional (and annoying) configuration step required to get SQLCLR Assemblies to load starting in SQL Server 2017, some people have been wondering what is going on with SQLCLR. Considering that this new restriction is the only real change to SQLCLR since… Continue reading SQLCLR vs SQL Server 2017, Part 8: Is SQLCLR Deprecated in Favor of Python or R (sp_execute_external_script)?
"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
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?
"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?
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
(last updated: 2019-03-31 @ 16:30 EST / 2019-03-31 @ 20:30 UTC ) 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… Continue reading SQLCLR vs. SQL Server 2017, Part 2: “CLR strict security” – Solution 1
The Good, the Bad, and the Ugle̅e̅ (need to avoid copyright infringement ;-) ) (last updated: 2018-10-22 @ 10:40 EDT / 2018-10-22 @ 14:40 UTC ) 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… Continue reading SQLCLR vs. SQL Server 2017, Part 1: “CLR strict security” – The Problem