Evaluates the effective permission of the current user on a securable.
Is the name of the securable. If the securable is the server itself, this value should be set to NULL. securable is a scalar expression of type sysname. There is no default.
Is the name of the class of securable against which the permission is tested. securable_class is a scalar expression of type nvarchar(60).
A nonnull scalar expression of type sysname that represents the permission name to be checked. There is no default. The permission name ANY is a wildcard.
An optional scalar expression of type sysname that represents the name of the securable sub-entity against which the permission is tested. The default is NULL.
An optional scalar expression of type nvarchar(60) that represent the class of securable subentity against which the permission is tested. The default is NULL.
This built-in function tests whether the current principal has a particular effective permission on a specified securable. An effective permission is any of the followoing:
A permission granted directly to the principal, and not denied.
A permission implied by a higher-level permission held by the principal and not denied.
A permission granted to a role or group of which the principal is a member, and not denied.
A permission held by a role or group of which the principal is a member, and not denied.
The permission evaluation is always performed in the security context of the caller. To determine whether some other user has an effective permission, the caller must have IMPERSONATE permission on that user.
For schema-level entities, one-, two-, or three-part nonnull names are accepted. For database-level entities a one-part name is accepted, with a null value meaning "current database". For the server itself, a null value (meaning "current server") is required. This function cannot check permissions on a linked server or on a Windows user for which no server-level principal has been created.
The following query will return a list of built-in securable classes:
SELECT class_desc FROM sys.fn_builtin_permissions(default)
The following collations are used:
Current database collation: Database-level securables that include securables not contained by a schema; one- or two-part schema-scoped securables; target database when using a three-part name.
master database collation: Server-level securables.
'ANY' is not supported for column-level checks. You must specify the appropriate permission.
A. Do I have the server-level VIEW SERVER STATE permission?
B. Am I able to IMPERSONATE server principal Ps?
C. Do I have any permissions in the current database?
D. Does database principal Pd have any permission in the current database?
Assume caller has IMPERSONATE permission on principal
EXECUTE AS user = 'Pd' GO SELECT has_perms_by_name(db_name(), 'DATABASE', 'ANY') GO REVERT GO
E. Can I create procedures and tables in schema S?
The following example requires
ALTER permission in
CREATE PROCEDURE permission in the database, and similarly for tables.
SELECT has_perms_by_name(db_name(), 'DATABASE', 'CREATE PROCEDURE') & has_perms_by_name('S', 'SCHEMA', 'ALTER') AS _can_create_procs, has_perms_by_name(db_name(), 'DATABASE', 'CREATE TABLE') & has_perms_by_name('S', 'SCHEMA', 'ALTER') AS _can_create_tables;
F. Which tables do I have SELECT permission on?
SELECT has_perms_by_name(SCHEMA_NAME(schema_id) + '.' + name, 'OBJECT', 'SELECT') AS have_select, * FROM sys.tables;
G. Do I have INSERT permission on the SalesPerson table in AdventureWorks?
The following example assumes
AdventureWorks is my current database context, and uses a two-part name.
SELECT has_perms_by_name('Sales.SalesPerson', 'OBJECT', 'INSERT')
The following example makes no assumptions about my current database context, and uses a three-part name.
SELECT has_perms_by_name('AdventureWorks.Sales.SalesPerson', 'OBJECT', 'INSERT')