This chapter introduced you to a powerful new technology, SQLCLR, that opens many new doors for the architect in you.
You saw how the CLR running inside the SQL Server behaves differently from the CLR you see running on any Windows machine. You saw how it puts security requirements on your code, and how you need to explicitly decide the specific functionality your SQLCLR code will require. You saw how SQLCLR code can be written either as a SQL Server project or as a simple class library. You also saw how to write common SQLCLR objects such as UDFs, TVFs, aggregates, stored procedures, and triggers and how to debug such code.
It’s true that SQLCLR gives you a lot of freedom, but with freedom comes responsibility. Like anything, it’s very tempting and easy to abuse or misuse SQLCLR for purposes it isn’t well suited for.
In the next and very last chapter of this book, I will discuss some of the biggest debates that surround ADO.NET. I will try and address best practices that will help you reason the correct decision in the specific circumstances.
In addition to other topics, the correct and proper use of SQLCLR will be touched upon. It’s extremely important to learn the responsibilities from the next chapter along with the possibilities that you learned in this chapter.
See you in the next and very last chapter, “ADO.NET Best Practices.”
Unable to display preview. Download preview PDF.