Applies to: SQL Server Azure SQL Managed Instance
SQL Server doesn't guarantee that lock hints will be honored in queries that access metadata through catalog views, compatibility views, information schema views, metadata-emitting built-in functions.
Internally, the SQL Server Database Engine only honors the READ COMMITTED isolation level for metadata access. If a transaction has an isolation level that is, for example, SERIALIZABLE and within the transaction, an attempt is made to access metadata by using catalog views or metadata-emitting built-in functions, those queries will run until they are completed as READ COMMITTED. However, under snapshot isolation, access to metadata might fail because of concurrent DDL operations. This is because metadata isn't versioned. Therefore, accessing the following under snapshot isolation might fail:
sp_help group of stored proceduresFor more information about isolation levels, see SET TRANSACTION ISOLATION LEVEL.
The following table provides a summary of metadata access under various isolation levels.
Isolation level Supported HonoredREAD UNCOMMITTED No Not guaranteed READ COMMITTED Yes Yes REPEATABLE READ No No SNAPSHOT ISOLATION No No SERIALIZABLE No No
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4