INSERT EXEC statement cannot be nested, the Simple Solution
Step-by-step guide to solve the "INSERT EXEC cannot be nested" problem by using a CLR when unit testing stored procedures using the tSQLt framework.
2022-08-19
39,312 reads
SQL CLR
How to Enable SQL Server CLR Integration using T-SQL
In this tip we look at how to enable SQL Server Common Runtime Language aka CLR using T-SQL commands.
2019-07-24
Getting The Most Out of SQL Server 2005 UDTs and UDAs
The CLR integration in SQL Server 2005 greatly expands on the capabilities of the SQL Server platform. One new area is the ability to build user-defined types and user-defined aggregates. Solomon Rutzky brings us a way to get around some of the limitations in this area with his SQL# toolkit.
2007-09-18
5,647 reads
SQLCLR Security and Designing for Reuse
SQL Server's CREATE ASSEMBLY statement lets you catalog code with one of three predefined security buckets. But under the covers, there are actually two distinct security models at play: Code Access Security and Host Protection, and you need to understand both.
2007-08-02
1,670 reads
Using CLR Integration in SQL 05 for Writing Stored Procedures
With SQL 2005 you can harness the power of a higher-level language to not only do more with stored procedures, but also save time by already knowing a popular .NET language.
2007-07-11
3,137 reads
Using CLR integration to compress BLOBs/CLOBs in SQL Server 2005
Working with large objects, BLOBs in SQL Server, has always been a little tedious. The forums are filled with questions on this topic. New authro Yoel Martinez brings us a more advanced looked at BLOBs in SQL Server 2005 with code and a technique for compressing large amounts of data to save space.
2008-01-11 (first published: 2007-01-30)
8,766 reads
CLR Inside Out
This article is meant to explore these architectural issues from the bottom up, and aims to guide you through this new world. In the long run, new programming models are likely to appear that will abstract away a lot of the challenges you will encounter.
2006-12-15
2,929 reads
Creating a generic audit trigger with SQL 2005 CLR
Auditing is becoming more important all the time for DBAs as regulations and requirements increase. Building auditing into your systems can be done a number of ways, but with SQL Server 2005, you have a new option. New author David Ziffer brings us a generic auditing CLR trigger.
2006-08-02
19,055 reads
Security in the CLR World Inside SQL Server
s running .NET Framework code within SQL Server 2005 exciting or a threat? Which is it? This article explores the security issues of SQLCLR code so that both developers and DBAs can make informed decisions about its use.
2006-06-15
2,774 reads
Geocoding with SQL Server 2005
Mapping services have become quite popular on the Internet and with many applications, but in order to use these, you need to map an address to a latitude and longtitude. Corey Bunch brings us a CLR example of how you can do this.
2006-05-01
19,025 reads
Blogs
Finding the Last Last Name in SQL: #SQLNewBlogger
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
SQL Server 2025 GAs Today
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Run SQL Server 2025 and SQL Server Management Studio on macOS Tahoe
Short version You want to get this running as fast as possible. Do these...
Forums
Email change does not work
I changed my email address in Edit Profile page, but it has no effect...
The case for "Understanding our business" training
Comments posted to this topic are about the item The case for "Understanding our...
Specifying the Collation
Comments posted to this topic are about the item Specifying the Collation
Question of the Day
Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers