I want to further validate comments made by a number of people. For demo purposes, this works fine, but it is a bad example of a real-world UDT. This point...

I understand that your primary intention is "to show how to use CLR integration in SQL Server to extend the engines functionality and provides an overview on what can be...

Actually, both are part of formatting the output (when printing the SQL) that do not affect the actual executed dynamic SQL.

However, I usually do this a little differently. First of...

I use a couple of phrases quite often when planning, developing, teaching, etc. One of them is "There are always exceptions to the rule." My other favorite is "It depends"....

Unless the client application is entirely metadata-driven (which is another topic of discussion in iteself), both stored procedures and dynamic SQL (parameterized queries) can both cause require client code to...

You are right, political and social aspects of any development project can have negative effects. Abuse, overuse, or miuse of stored procedures can have a detrimental effect. I know it...

From SQL Server's standpoint, parameterized queries are the same as dynamic SQL. Yes, parameterized queries themselves do away with the possibility of SQL injection attacks, but you still must open...

A better version of the code from my previous post

SELECT T.TABLE_SCHEMA, T.TABLE_NAME, C.COLUMN_NAME, C.DATA_TYPE,

       IDENT_CURRENT(T.TABLE_SCHEMA + '.' + T.TABLE_NAME) [CURRENT_IDENTITY_VALUE]

FROM INFORMATION_SCHEMA.TABLES AS T (NOLOCK)

        INNER JOIN INFORMATION_SCHEMA.COLUMNS AS C (NOLOCK) 

        ON C.TABLE_SCHEMA...

Hear! Hear!

Microsoft recommends that you use the Information Schema views instead of the system tables when possible. To quote SQL Server 2000 Books Online: "To obtain meta data, use...