CLR Integration vs. Extended Stored Procedures

CLR Integration vs. Extended Stored Procedures.


CLR Integration Extended Stored Procedures
Memory management, threads scheduling, and synchronization services are deeply integrated between managed code of CLR and SQL Server.They are built to perform functionality which is not possible with T-SQL stored procedures.
Do not compromise integrity of SQL Server process as it is managed type safe code.Compromise integrity of SQL Server process
Not supported by older versions of SQL ServerSupported by older versions of SQL Server
Can be written using any .NET compliant language. Can be only written using c/c++
Slower performanceFaster performance

CLR Integration vs. Extended Stored Procedures.

CLR Integration provides a more convenient and robust solution to Extended stored procedures for implementing server side logic. Using Common Language Runtime integration allows the results constructed by the function to be queried in SELECT statements by embedding them in the FROM clause. CLR code objects can be written in .NET languages which are safe and fast. CLR code can work with data types like XML, varchar binary.
How to configure CLR for SQL Server?
CLR by default is not configured in SQL server. It needs to be explicit ally configured using sp_configure syntax. This is shown as below:........
How to create functions in SQL Server using .NET?
Functions in SQL server can be created using the .NET common language interface or CLR. The functions code is written and then complied into a .NET assembly to deploy on the SQL server.........
Full syntax of Select Statement with examples
SELECT is used to select a specific or ALL columns / rows from a table.......
Post your comment