This topic has not yet been rated - Rate this topic

Security Catalog Views (Transact-SQL)

Security information is exposed in catalog views that are optimized for performance and utility. When possible, use the following catalog views to access catalog metadata.

Database-Level Views

sys.database_permissions	sys.database_role_members
sys.database_principals	sys.master_key_passwords

Server-Level Views

sys.server_permissions	sys.sql_logins
sys.server_principals	sys.system_components_surface_area_configuration
sys.server_role_members	.

Encryption Views

sys.asymmetric_keys	sys.crypt_properties
sys.certificates	sys.key_encryptions
sys.credentials	sys.symmetric_keys
sys.cryptographic_providers (Transact-SQL)	.

SQL Server Audit Views

sys.server_audits (Transact-SQL)	sys.server_file_audits (Transact-SQL)
sys.server_audit_specifications (Transact-SQL)	sys.server_audit_specification_details (Transact-SQL)
sys.database_audit_specifications (Transact-SQL)	sys.database_audit_specification_details (Transact-SQL) _specification_details

Permissions

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.

Reference

Catalog Views (Transact-SQL)

Security-Related Dynamic Management Views and Functions (Transact-SQL)

Concepts

Security and Protection (Database Engine)

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Content Add

FAQ