MUSINGS

Getting XML Serialization and Webservices to work with SQL CLR

Getting XML Serialization and Webservices to work with SQL CLR

Microsoft SQL server has built-in security which prevents the dynamic loading of serialized assemblies. What this basically means is that an assembly which utilises Webservices and XML.Serialization will dynamically load the code and compile at runtime and SQL Server doesn’t like that. This is the error you will receive when running functions or procedures in such an assembly. Read more about Getting XML Serialization and Webservices to work with SQL CLR

Adding the Microsoft Exchange Webservices SQL CLR assembly the easy way

Adding the Microsoft Exchange Webservices SQL CLR assembly the easy way

If you try and load the Microsoft Exchange Web Services dll (Microsoft.Exchange.WebServices.dll) as an assembly in Microsoft SQL Server, you will receive errors relating to dependent assemblies not being loaded in the SQL catalog.
The MSDN article for CREATE ASSEMBLY states

Besides the root assembly specified by assembly_name, SQL Server tries to upload any assemblies that are referenced by the root assembly being uploaded. If a referenced assembly is already uploaded to the database because of an earlier CREATE ASSEMBLY statement, this assembly is not uploaded but is available to the root assembly. If a dependent assembly was not previously uploaded, but SQL Server cannot locate its manifest file in the source directory, CREATE ASSEMBLY returns an error.

BUT this isn’t always the case. The first rule is Read more about Adding the Microsoft Exchange Webservices SQL CLR assembly the easy way

SQL date handling, or prior to 2008 the world didn’t begin until 1753

SQL date handling, or prior to 2008 the world didn’t begin until 1753

If you ever need to transfer data between an Oracle instance and Microsoft SQL Server 2005, you’ll need to be aware of the differences between data types.¬†In some instances¬†this will require massaging the data so it’ll “fit” the schema at the destination, while maintaining the data integrity.

An interesting example of this is the date and time data types. Read more about SQL date handling, or prior to 2008 the world didn’t begin until 1753