sqlclr

SQL Server allows you to create CLR functions, stored procedures, user types and other objects, for purpose that are really complex to be done inside SQL. But, can someone compare those two things: TSQL Object and CLR Object, in sense of performance, benefits, and so on. What are real situations for usage CLR objects? Is there any best practices proposition for their usage? What are real situations for usage CLR objects? SQL Server lacks an aggregate string concatenation function. This bizarre oversight leads to all manner of complicated work-arounds. Creating and using a custom CLR aggregate

I have the following type of code in my data layer, which can be called from a console app, windows app, etc, with the proper connection string being read from the corresponding caller's App.Config file: public static udsDataset GetDataset(int datasetID) { string connectionString = ConfigurationManager.ConnectionStrings["ConnectionString"].ConnectionString; string sql = @"select * from Dataset WHERE DatasetID=@datasetID"; using (SqlConnection conn = new SqlConnection(connectionString)) { // Dapper query: return conn.Query<udsDataset>(sql, new {datasetID } ).First(); } } I now want to call this

I am in the process of migrating a SQL Server 2008 to 2012 and running into challenges in creating some of the necessary assemblies for a CLR routine. The routine takes a dependency on stdole.dll , but I am unable to create this assembly. My code is as follows: ALTER DATABASE main SET TRUSTWORTHY ON; create assembly [stdole] from 'C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies\stdole.dll' WITH PERMISSION_SET = unsafe I am receiving the following error: Warning: The Microsoft .NET Framework assembly 'stdole, version=7.0.3300.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a.'