sys.sql_modules (Transact-SQL)


THIS TOPIC APPLIES TO: yesSQL Server (starting with 2008)yesAzure SQL DatabaseyesAzure SQL Data Warehouse yesParallel Data Warehouse

Returns a row for each object that is an SQL language-defined module in SQL Server, including natively compiled scalar user-defined function. Objects of type P, RF, V, TR, FN, IF, TF, and R have an associated SQL module. Stand-alone defaults, objects of type D, also have an SQL module definition in this view. For a description of these types, see the type column in the sys.objects catalog view.

For more information, see Scalar User-Defined Functions for In-Memory OLTP.

Column nameData typeDescription
object_idintID of the object of the containing object. Is unique within a database.
definitionnvarchar(max)SQL text that defines this module.

NULL = Encrypted.
uses_ansi_nullsbitModule was created with SET ANSI_NULLS ON.

Will always be = 0 for rules and defaults.
uses_quoted_identifierbitModule was created with SET QUOTED_IDENTIFIER ON.
is_schema_boundbitModule was created with SCHEMABINDING option.

Always contains a value of 1 for natively compiled stored procedures.
uses_database_collationbit1 = Schema-bound module definition depends on the default-collation of the database for correct evaluation; otherwise, 0. Such a dependency prevents changing the database's default collation.
is_recompiledbitProcedure was created WITH RECOMPILE option.
null_on_null_inputbitModule was declared to produce a NULL output on any NULL input.
execute_as_principal_idIntID of the EXECUTE AS database principal.

NULL by default or if EXECUTE AS CALLER.

ID of the specified principal if EXECUTE AS SELF or EXECUTE AS <principal>.

uses_native_compilationbitApplies to: SQL Server 2014 through SQL Server 2014.

0 = not natively compiled

1 = is natively compiled

The default value is 0.

The SQL expression for a DEFAULT constraint, object of type D, is found in the sys.default_constraints catalog view. The SQL expression for a CHECK constraint, object of type C, is found in the sys.check_constraints catalog view.

This information is also described in sys.dm_db_uncontained_entities (Transact-SQL).

The visibility of the metadata in catalog views is limited to securables that a user either owns or on which the user has been granted some permission. For more information, see Metadata Visibility Configuration.

The following example returns the name, type, and definition of each module in the current database.

SELECT sm.object_id, OBJECT_NAME(sm.object_id) AS object_name, o.type, o.type_desc, sm.definition  
FROM sys.sql_modules AS sm  
JOIN sys.objects AS o ON sm.object_id = o.object_id  
ORDER BY o.type;  

Catalog Views (Transact-SQL)
Object Catalog Views (Transact-SQL)
Querying the SQL Server System Catalog FAQ
In-Memory OLTP (In-Memory Optimization)

Community Additions