TechNet
Export (0) Print
Expand All
Collapse the table of content
Expand the table of content
Expand Minimize

Security Catalog Views (Transact-SQL)

 

THIS TOPIC APPLIES TO:yesSQL Server (starting with 2008)noAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

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.

sys.database_permissionssys.master_key_passwords
sys.database_principalssys.user_token
sys.database_role_members
sys.credentialssys.server_principals
sys.login_tokensys.server_role_members
sys.securable_classessys.sql_logins
sys.server_permissionssys.system_components_surface_area_configuration
sys.asymmetric_keyssys.cryptographic_providers
sys.certificatessys.key_encryptions
sys.column_encryption_key_valuessys.openkeys
sys.column_encryption_keyssys.security_policies (Transact-SQL)
sys.column_master_key_definitionssys.security_predicates (Transact-SQL)
sys.crypt_propertiessys.symmetric_keys
sys.server_auditssys.server_file_audits
sys.server_audit_specificationssys.server_audit_specifications_details
sys.database_ audit_specificationssys.audit_database_specification_details

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.

Catalog Views (Transact-SQL)
Security Center for SQL Server Database Engine and Azure SQL Database
Security-Related Dynamic Management Views and Functions (Transact-SQL)

Community Additions

ADD
Show:
© 2016 Microsoft