Accomplishing this can be done in a few ways and depends on what version of SQL Server you are using (SQL Server 2017 introduced a new complication) and if you are using Visual Studio / SSDT / SqlPackage`exe for deployment. You should instead sign the Assembly, then create an Asymmetric Key in master from the DLL, then create a Login from that Asymmetric Key, and finally grant the EXTERNAL ACCESS ASSEMBLY permission to that Login. It won't automatically give you a strongly typed object, but it is guaranteed to work across all version of SQL Server.Īlso, the advice in that post to enable TRUSTWORTHY is bad advice. NET Framework Libraries list.įor doing such things, I usually recommend using the plain 'ol HttpWebRequest / HttpWebResponse classes and handling the creation and parsing of the XML manually (well, using available.
You can do web service calls in SQLCLR, but only using libraries in the Supported. NET Framework libraries that you need to manually load into SQLServer), then that isn't going to work. But regardless, if you are relying on the ServiceModel library (or any other. Does anyone have other options on how to satisfy this requirement? I tried some PowerShell scripts that supposedly would install it, but nothing worked.It helps to know what version of SQL Server you are on. One work around I found was I installed SSMS 18 which added it, but again I'd rather not install any dev tools on the web servers just to get SMO. I would rather not install Visual Studio on our Dynamics 365 web servers just to get this package. I was able to get CLR Type installed using SQL 2017 Feature Pack, but they have removed SMO from this, it's only installable through a Nuget package in Visual Studio from what I'm seeing. So when using it I get errors about missing CLR Type and SMO for Sql 2017. Using a Setup script I can install the latest update (0.22) during installation, but the installer only installs the SQL components for SQL 2016 and not 2017. RTM is only compatible with SQL 2016, but as of update 0.03 it does support SQL 2017.
Here's the scenario, we're installing Microsoft Dynamics 365 (Formerly CRM) v9 On Prem on SQL 2017.
0 kommentar(er)
