The wrox.com code downloads for this chapter are found at www.wrox.com/go/prosql2014admin on the Download Code tab. The code is in the Chapter 7 download and individually named according to the names throughout the chapter.
SQL Server developers first saw the integration of the .NET Common Language Runtime (CLR) with the release of SQL Server 2005. As the .NET Framework has evolved through its versions, SQL Server has continued to support integration of CLR. CLR provides great benefits to developers and database administrators, and is a valuable tool to have in your arsenal.
Although a detailed discussion of writing managed code using a .NET programming language such as C# is beyond the scope of this chapter, you learn to create and deploy a simple .NET assembly and enable it for SQL integration. You then look at when a SQL Server CLR (SQLCLR) solution provides a better alternative to a traditional T-SQL solution. This chapter also discusses SQLCLR performance and security, which are critical issues to consider when deciding whether to use SQLCLR over traditional T-SQL.
With the integration of the .NET Framework CLR components in SQL Server, developers have the flexibility to write stored procedures, triggers, user-defined types and functions, ...