Skip to content

Latest commit

 

History

History
92 lines (67 loc) · 3.55 KB

File metadata and controls

92 lines (67 loc) · 3.55 KB
title CREATE APPLICATION ROLE (Transact-SQL)
description CREATE APPLICATION ROLE (Transact-SQL)
author VanMSFT
ms.author vanto
ms.reviewer randolphwest
ms.date 11/18/2025
ms.service sql
ms.subservice t-sql
ms.topic reference
ms.custom
ignite-2025
f1_keywords
APPLICATION_ROLE_TSQL
CREATE APPLICATION ROLE
sql13.swb.applicationrole.permissions.f1
APPLICATION
APPLICATION ROLE
CREATE_APPLICATION_ROLE_TSQL
APPLICATION_TSQL
helpviewer_keywords
CREATE APPLICATION ROLE statement
application roles [SQL Server], creating
dev_langs
TSQL

CREATE APPLICATION ROLE (Transact-SQL)

[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance]

Adds an application role to the current database.

:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: Transact-SQL syntax conventions

Syntax

CREATE APPLICATION ROLE application_role_name
    WITH PASSWORD = 'password' [ , DEFAULT_SCHEMA = schema_name ]

Arguments

application_role_name

Specifies the name of the application role. This name must not already be used to refer to any principal in the database.

PASSWORD = 'password'

Specifies the password that database users will use to activate the application role. You should always use strong passwords. password must meet the Windows password policy requirements of the computer that is running the instance of [!INCLUDE ssNoVersion].

DEFAULT_SCHEMA = schema_name

Specifies the first schema that will be searched by the server when it resolves the names of objects for this role. If DEFAULT_SCHEMA is left undefined, the application role will use dbo as its default schema. schema_name can be a schema that doesn't exist in the database.

Remarks

Important

Password complexity is checked when application role passwords are set. Applications that invoke application roles must store their passwords. Application role passwords should always be stored encrypted.

Application roles are visible in the sys.database_principals catalog view.

For information about how to use application roles, see Application Roles.

Note

[!INCLUDE ssCautionUserSchema]

[!INCLUDE encryption-algorithm-history-md]

Permissions

Requires ALTER ANY APPLICATION ROLE permission on the database.

Examples

The following example creates an application role called weekly_receipts that has the password 987Gbv876sPYY5m23 and Sales as its default schema.

CREATE APPLICATION ROLE weekly_receipts
    WITH PASSWORD = '987G^bv876sPY)Y5m23'
    , DEFAULT_SCHEMA = Sales;
GO

Related content