--- description: "CREATE LOGIN (Transact-SQL)" title: "CREATE LOGIN (Transact-SQL) | Microsoft Docs" ms.custom: "" ms.date: 07/29/2020 ms.prod: sql ms.prod_service: "database-engine, sql-database, sql-data-warehouse, pdw" ms.reviewer: "" ms.technology: t-sql ms.topic: reference f1_keywords: - "CREATE_LOGIN_TSQL" - "CREATE LOGIN" - "LOGIN_TSQL" - "LOGIN" dev_langs: - "TSQL" helpviewer_keywords: - "passwords [SQL Server], logins" - "mapping logins [SQL Server]" - "logins [SQL Server], creating" - "CREATE LOGIN statement" - "permissions [SQL Server], logins" - "Windows domain accounts [SQL Server]" - "re-hashing passwords" - "certificates [SQL Server], logins" ms.assetid: eb737149-7c92-4552-946b-91085d8b1b01 author: VanMSFT ms.author: vanto monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current" --- # CREATE LOGIN (Transact-SQL) Creates a login for SQL Server, SQL Database, Azure Synapse Analytics, or Analytics Platform System databases. Click one of the following tabs for the syntax, arguments, remarks, permissions, and examples for a particular version. CREATE LOGIN participates in transactions. If CREATE LOGIN is executed within a transaction and the transaction is rolled back, then login creation is rolled back. If executed within a transaction, the created login cannot be used until the transaction is committed. For more information about the syntax conventions, see [Transact-SQL Syntax Conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md). [!INCLUDE[select-product](../../includes/select-product.md)] ::: moniker range=">=sql-server-2016||>=sql-server-linux-2017" :::row::: :::column::: **_\* SQL Server \*_**   :::column-end::: :::column::: [Azure SQL Database](create-login-transact-sql.md?view=azuresqldb-current&preserve-view=true) :::column-end::: :::column::: [Azure SQL
Managed Instance](create-login-transact-sql.md?view=azuresqldb-mi-current&preserve-view=true) :::column-end::: :::column::: [Azure Synapse
Analytics](create-login-transact-sql.md?view=azure-sqldw-latest&preserve-view=true) :::column-end::: :::column::: [Analytics Platform
System (PDW)](create-login-transact-sql.md?view=aps-pdw-2016&preserve-view=true) :::column-end::: :::row-end:::   ## SQL Server ## Syntax ```syntaxsql -- Syntax for SQL Server CREATE LOGIN login_name { WITH | FROM } ::= PASSWORD = { 'password' | hashed_password HASHED } [ MUST_CHANGE ] [ , [ ,... ] ] ::= SID = sid | DEFAULT_DATABASE = database | DEFAULT_LANGUAGE = language | CHECK_EXPIRATION = { ON | OFF} | CHECK_POLICY = { ON | OFF} | CREDENTIAL = credential_name ::= WINDOWS [ WITH [ ,... ] ] | CERTIFICATE certname | ASYMMETRIC KEY asym_key_name ::= DEFAULT_DATABASE = database | DEFAULT_LANGUAGE = language ``` ## Arguments *login_name* Specifies the name of the login that is created. There are four types of logins: SQL Server logins, Windows logins, certificate-mapped logins, and asymmetric key-mapped logins. When you are creating logins that are mapped from a Windows domain account, you must use the pre-Windows 2000 user logon name in the format [\\\]. You cannot use a UPN in the format login_name@DomainName. For an example, see example D later in this article. Authentication logins are type **sysname** and must conform to the rules for [Identifiers](../../relational-databases/databases/database-identifiers.md) and cannot contain a '**\\**'. Windows logins can contain a '**\\**'. Logins based on Active Directory users, are limited to names of fewer than 21 characters. PASSWORD **=**'*password*' Applies to SQL Server logins only. Specifies the password for the login that is being created. Use a strong password. For more information, see [Strong Passwords](../../relational-databases/security/strong-passwords.md) and [Password Policy](../../relational-databases/security/password-policy.md). Beginning with SQL Server 2012 (11.x), stored password information is calculated using SHA-512 of the salted password. Passwords are case-sensitive. Passwords should always be at least eight characters long, and cannot exceed 128 characters. Passwords can include a-z, A-Z, 0-9, and most non-alphanumeric characters. Passwords cannot contain single quotes, or the *login_name*. PASSWORD **=** *hashed\_password* Applies to the HASHED keyword only. Specifies the hashed value of the password for the login that is being created. HASHED Applies to SQL Server logins only. Specifies that the password entered after the PASSWORD argument is already hashed. If this option is not selected, the string entered as password is hashed before it is stored in the database. This option should only be used for migrating databases from one server to another. Do not use the HASHED option to create new logins. The HASHED option cannot be used with hashes created by SQL 7 or earlier. MUST_CHANGE Applies to SQL Server logins only. If this option is included, SQL Server prompts the user for a new password the first time the new login is used. CREDENTIAL **=**_credential\_name_ The name of a credential to be mapped to the new SQL Server login. The credential must already exist in the server. Currently this option only links the credential to a login. A credential cannot be mapped to the System Administrator (sa) login. SID = *sid* Used to recreate a login. Applies to SQL Server authentication logins only, not Windows authentication logins. Specifies the SID of the new SQL Server authentication login. If this option is not used, SQL Server automatically assigns a SID. The SID structure depends on the SQL Server version. SQL Server login SID: a 16 byte (**binary(16)**) literal value based on a GUID. For example, `SID = 0x14585E90117152449347750164BA00A7`. DEFAULT_DATABASE **=**_database_ Specifies the default database to be assigned to the login. If this option is not included, the default database is set to master. DEFAULT_LANGUAGE **=**_language_ Specifies the default language to be assigned to the login. If this option is not included, the default language is set to the current default language of the server. If the default language of the server is later changed, the default language of the login remains unchanged. CHECK_EXPIRATION **=** { ON | **OFF** } Applies to SQL Server logins only. Specifies whether password expiration policy should be enforced on this login. The default value is OFF. CHECK_POLICY **=** { **ON** | OFF } Applies to SQL Server logins only. Specifies that the Windows password policies of the computer on which SQL Server is running should be enforced on this login. The default value is ON. If the Windows policy requires strong passwords, passwords must contain at least three of the following four characteristics: - An uppercase character (A-Z). - A lowercase character (a-z). - A digit (0-9). - One of the non-alphanumeric characters, such as a space, _, @, *, ^, %, !, $, #, or &. WINDOWS Specifies that the login be mapped to a Windows login. CERTIFICATE *certname* Specifies the name of a certificate to be associated with this login. This certificate must already occur in the master database. ASYMMETRIC KEY *asym_key_name* Specifies the name of an asymmetric key to be associated with this login. This key must already occur in the master database. ## Remarks - Passwords are case-sensitive. - Prehashing of passwords is supported only when you are creating SQL Server logins. - If MUST_CHANGE is specified, CHECK_EXPIRATION and CHECK_POLICY must be set to ON. Otherwise, the statement will fail. - A combination of CHECK_POLICY = OFF and CHECK_EXPIRATION = ON is not supported. - When CHECK_POLICY is set to OFF, *lockout_time* is reset and CHECK_EXPIRATION is set to OFF. > [!IMPORTANT] > CHECK_EXPIRATION and CHECK_POLICY are only enforced on Windows Server 2003 and later. For more information, see [Password Policy](../../relational-databases/security/password-policy.md). - Logins created from certificates or asymmetric keys are used only for code signing. They cannot be used to connect to SQL Server. You can create a login from a certificate or asymmetric key only when the certificate or asymmetric key already exists in master. - For a script to transfer logins, see [How to transfer the logins and the passwords between instances of SQL Server 2005 and SQL Server 2008](https://support.microsoft.com/kb/918992). - Creating a login automatically enables the new login and grants the login the server level **CONNECT SQL** permission. - The server's [authentication mode](../../relational-databases/security/choose-an-authentication-mode.md) must match the login type to permit access. - For information about designing a permissions system, see [Getting Started with Database Engine Permissions](../../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md). ## Permissions - Only users with **ALTER ANY LOGIN** permission on the server or membership in the **securityadmin** fixed server role can create logins. For more information, see [Server-Level Roles](/azure/sql-database/sql-database-manage-logins#groups-and-roles) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md). - If the **CREDENTIAL** option is used, also requires **ALTER ANY CREDENTIAL** permission on the server. ## After creating a login After creating a login, the login can connect to SQL Server, but only has the permissions granted to the **public** role. Consider performing some of the following activities. - To connect to a database, create a database user for the login. For more information, see [CREATE USER](../../t-sql/statements/create-user-transact-sql.md). - Create a user-defined server role by using [CREATE SERVER ROLE](../../t-sql/statements/create-server-role-transact-sql.md). Use **ALTER SERVER ROLE** ... **ADD MEMBER** to add the new login to the user-defined server role. For more information, see [CREATE SERVER ROLE](../../t-sql/statements/create-server-role-transact-sql.md) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md). - Use **sp_addsrvrolemember** to add the login to a fixed server role. For more information, see [Server-Level Roles](../../relational-databases/security/authentication-access/server-level-roles.md) and [sp_addsrvrolemember](../../relational-databases/system-stored-procedures/sp-addsrvrolemember-transact-sql.md). - Use the **GRANT** statement, to grant server-level permissions to the new login or to a role containing the login. For more information, see [GRANT](../../t-sql/statements/grant-transact-sql.md). ## Examples ### A. Creating a login with a password The following example creates a login for a particular user and assigns a password. ```sql CREATE LOGIN WITH PASSWORD = ''; GO ``` ### B. Creating a login with a password that must be changed The following example creates a login for a particular user and assigns a password. The `MUST_CHANGE` option requires users to change this password the first time they connect to the server. **Applies to**: [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] and later. ```sql CREATE LOGIN WITH PASSWORD = '' MUST_CHANGE, CHECK_EXPIRATION = ON; GO ``` > [!NOTE] > The MUST_CHANGE option cannot be used when CHECK_EXPIRATION is OFF. ### C. Creating a login mapped to a credential The following example creates the login for a particular user, using the user. This login is mapped to the credential. **Applies to**: [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] and later. ```sql CREATE LOGIN WITH PASSWORD = '', CREDENTIAL = ; GO ``` ### D. Creating a login from a certificate The following example creates login for a particular user from a certificate in master. **Applies to**: [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] and later. ```sql USE MASTER; CREATE CERTIFICATE WITH SUBJECT = ' certificate in master database', EXPIRY_DATE = '12/05/2025'; GO CREATE LOGIN FROM CERTIFICATE ; GO ``` ### E. Creating a login from a Windows domain account The following example creates a login from a Windows domain account. **Applies to**: [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] and later. ```sql CREATE LOGIN [\] FROM WINDOWS; GO ``` ### F. Creating a login from a SID The following example first creates a SQL Server authentication login and determines the SID of the login. ```sql CREATE LOGIN TestLogin WITH PASSWORD = 'SuperSecret52&&'; SELECT name, sid FROM sys.sql_logins WHERE name = 'TestLogin'; GO ``` My query returns 0x241C11948AEEB749B0D22646DB1A19F2 as the SID. Your query will return a different value. The following statements delete the login, and then recreate the login. Use the SID from your previous query. ```sql DROP LOGIN TestLogin; GO CREATE LOGIN TestLogin WITH PASSWORD = 'SuperSecret52&&', SID = 0x241C11948AEEB749B0D22646DB1A19F2; SELECT * FROM sys.sql_logins WHERE name = 'TestLogin'; GO ``` ### G. Creating a login with multiple arguments The following example shows how to string multiple arguments together using commas between each argument. ```sql CREATE LOGIN [MyUser] WITH PASSWORD = 'MyPassword', DEFAULT_DATABASE = MyDatabase, CHECK_POLICY = OFF, CHECK_EXPIRATION = OFF ; ``` ## See Also - [Getting Started with Database Engine Permissions](../../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md) - [Principals](../../relational-databases/security/authentication-access/principals-database-engine.md) - [Password Policy](../../relational-databases/security/password-policy.md) - [ALTER LOGIN](../../t-sql/statements/alter-login-transact-sql.md) - [DROP LOGIN](../../t-sql/statements/drop-login-transact-sql.md) - [EVENTDATA](../../t-sql/functions/eventdata-transact-sql.md) - [Create a Login](../../relational-databases/security/authentication-access/create-a-login.md) ::: moniker-end ::: moniker range="=azuresqldb-current" :::row::: :::column::: [SQL Server](create-login-transact-sql.md?view=sql-server-ver15&preserve-view=true) :::column-end::: :::column::: **_\* Azure SQL Database \*_** :::column-end::: :::column::: [Azure SQL
Managed Instance](create-login-transact-sql.md?view=azuresqldb-mi-current&preserve-view=true) :::column-end::: :::column::: [Azure Synapse
Analytics](create-login-transact-sql.md?view=azure-sqldw-latest&preserve-view=true) :::column-end::: :::column::: [Analytics Platform
System (PDW)](create-login-transact-sql.md?view=aps-pdw-2016&preserve-view=true) :::column-end::: :::row-end:::   ## SQL Database ## Syntax ```syntaxsql -- Syntax for Azure SQL Database CREATE LOGIN login_name { WITH } ::= PASSWORD = { 'password' } [ , SID = sid ] ``` ## Arguments *login_name* Specifies the name of the login that is created. Single and pooled databases in Azure SQL Database and databases in [!INCLUDE[ssSDW](../../includes/sssdwfull-md.md)] supports only SQL logins. To create accounts for Azure Active Directory users or to create user accounts not associated with a login, use the [CREATE USER](create-user-transact-sql.md) statement. For more information, see [Manage Logins in Azure SQL Database](/azure/sql-database/sql-database-manage-logins). PASSWORD **='**password**'* Specifies the password for the SQL login that is being created. Use a strong password. For more information, see [Strong Passwords](../../relational-databases/security/strong-passwords.md) and [Password Policy](../../relational-databases/security/password-policy.md). Beginning with [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], stored password information is calculated using SHA-512 of the salted password. Passwords are case-sensitive. Passwords should always be at least eight characters long, and cannot exceed 128 characters. Passwords can include a-z, A-Z, 0-9, and most non-alphanumeric characters. Passwords cannot contain single quotes, or the *login_name*. SID = *sid* Used to recreate a login. Applies to SQL Server authentication logins only, not Windows authentication logins. Specifies the SID of the new SQL Server authentication login. If this option is not used, SQL Server automatically assigns a SID. The SID structure depends on the SQL Server version. For SQL Database, this is a 32 byte (**binary(32)**) literal consisting of `0x01060000000000640000000000000000` plus 16 bytes representing a GUID. For example, `SID = 0x0106000000000064000000000000000014585E90117152449347750164BA00A7`. ## Remarks - Passwords are case-sensitive. - Creating a login automatically enables the new login and grants the login the server level **CONNECT SQL** permission. > [!IMPORTANT] > See [Manage Logins in Azure SQL Database](/azure/sql-database/sql-database-manage-logins) for information about working with logins and users in Azure SQL Database. ## Login ### SQL Database Logins The **CREATE LOGIN** statement must be the only statement in a batch. In some methods of connecting to SQL Database, such as **sqlcmd**, you must append the SQL Database server name to the login name in the connection string by using the *\*@*\* notation. For example, if your login is `login1` and the fully qualified name of the SQL Database server is `servername.database.windows.net`, the *username* parameter of the connection string should be `login1@servername`. Because the total length of the *username* parameter is 128 characters, *login_name* is limited to 127 characters minus the length of the server name. In the example, `login_name` can only be 117 characters long because `servername` is 10 characters. In SQL Database, you must be connected to the master database with the appropriate permissions to create a login. For more information, see [Create additional logins and users having administrative permissions](/azure/sql-database/sql-database-manage-logins#create-additional-logins-and-users-having-administrative-permissions). SQL Server rules allow you create a SQL Server authentication login in the format \@\. If your [!INCLUDE[ssSDS](../../includes/sssds-md.md)] server is **myazureserver** and your login is **myemail@live.com**, then you must supply your login as **myemail@live.com@myazureserver**. In SQL Database, login data required to authenticate a connection and server-level firewall rules is temporarily cached in each database. This cache is periodically refreshed. To force a refresh of the authentication cache and make sure that a database has the latest version of the logins table, execute [DBCC FLUSHAUTHCACHE](../../t-sql/database-console-commands/dbcc-flushauthcache-transact-sql.md). ## Permissions Only the server-level principal login (created by the provisioning process) or members of the `loginmanager` database role in the master database can create new logins. For more information, see [Create additional logins and users having administrative permissions](/azure/sql-database/sql-database-manage-logins#create-additional-logins-and-users-having-administrative-permissions). ## Examples ### A. Creating a login with a password The following example creates a login for a particular user and assigns a password. ```sql CREATE LOGIN WITH PASSWORD = ''; GO ``` ### B. Creating a login from a SID The following example first creates a SQL Server authentication login and determines the SID of the login. ```sql CREATE LOGIN TestLogin WITH PASSWORD = 'SuperSecret52&&'; SELECT name, sid FROM sys.sql_logins WHERE name = 'TestLogin'; GO ``` My query returns 0x241C11948AEEB749B0D22646DB1A19F2 as the SID. Your query will return a different value. The following statements delete the login, and then recreate the login. Use the SID from your previous query. ```sql DROP LOGIN TestLogin; GO CREATE LOGIN TestLogin WITH PASSWORD = 'SuperSecret52&&', SID = 0x241C11948AEEB749B0D22646DB1A19F2; SELECT * FROM sys.sql_logins WHERE name = 'TestLogin'; GO ``` ## See Also - [Getting Started with Database Engine Permissions](../../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md) - [Principals](../../relational-databases/security/authentication-access/principals-database-engine.md) - [Password Policy](../../relational-databases/security/password-policy.md) - [ALTER LOGIN](../../t-sql/statements/alter-login-transact-sql.md) - [DROP LOGIN](../../t-sql/statements/drop-login-transact-sql.md) - [EVENTDATA](../../t-sql/functions/eventdata-transact-sql.md) - [Create a Login](../../relational-databases/security/authentication-access/create-a-login.md) ::: moniker-end ::: moniker range="=azuresqldb-mi-current" :::row::: :::column::: [SQL Server](create-login-transact-sql.md?view=sql-server-ver15&preserve-view=true) :::column-end::: :::column::: [Azure SQL Database](create-login-transact-sql.md?view=azuresqldb-current&preserve-view=true) :::column-end::: :::column::: **_\* Azure SQL
Managed Instance \*_** :::column-end::: :::column::: [Azure Synapse
Analytics](create-login-transact-sql.md?view=azure-sqldw-latest&preserve-view=true) :::column-end::: :::column::: [Analytics Platform
System (PDW)](create-login-transact-sql.md?view=aps-pdw-2016&preserve-view=true) :::column-end::: :::row-end:::   ## Azure SQL Managed Instance ## Syntax ```syntaxsql -- Syntax for Azure SQL Managed Instance CREATE LOGIN login_name [FROM EXTERNAL PROVIDER] { WITH [,..]} ::= PASSWORD = {'password'} | SID = sid | DEFAULT_DATABASE = database | DEFAULT_LANGUAGE = language ``` ## Arguments *login_name* When used with the **FROM EXTERNAL PROVIDER** clause, the login specifies the Azure Active Directory (AD) Principal, which is an Azure AD user, group, or application. Otherwise, the login represents the name of the SQL login that was created. FROM EXTERNAL PROVIDER
Specifies that the login is for Azure AD Authentication. PASSWORD **=** '*password*' Specifies the password for the SQL login that is being created. Use a strong password. For more information, see [Strong Passwords](../../relational-databases/security/strong-passwords.md) and [Password Policy](../../relational-databases/security/password-policy.md). Beginning with [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], stored password information is calculated using SHA-512 of the salted password. Passwords are case-sensitive. Passwords should always be at least ten characters long, and cannot exceed 128 characters. Passwords can include a-z, A-Z, 0-9, and most non-alphanumeric characters. Passwords cannot contain single quotes, or the *login_name*. SID **=** *sid* Used to recreate a login. Applies to SQL Server authentication logins only. Specifies the SID of the new SQL Server authentication login. If this option is not used, SQL Server automatically assigns a SID. The SID structure depends on the SQL Server version. For SQL Database, this is a 32 byte (**binary(32)**) literal consisting of `0x01060000000000640000000000000000` plus 16 bytes representing a GUID. For example, `SID = 0x0106000000000064000000000000000014585E90117152449347750164BA00A7`. ## Remarks - Passwords are case-sensitive. - New syntax is introduced for the creation of server-level principals mapped to Azure AD accounts (**FROM EXTERNAL PROVIDER**) - When **FROM EXTERNAL PROVIDER** is specified: - The login_name must represent an existing Azure AD account (user, group, or application) that is accessible in Azure AD by the current Azure SQL Managed Instance. For Azure AD principals, the CREATE LOGIN syntax requires: - UserPrincipalName of the Azure AD object for Azure AD Users. - DisplayName of Azure AD object for Azure AD Groups and Azure AD Applications. - The **PASSWORD** option cannot be used. - By default, when the **FROM EXTERNAL PROVIDER** clause is omitted, a regular SQL login is created. - Azure AD logins are visible in sys.server_principals, with type column value set to **E** and type_desc set to **EXTERNAL_LOGIN** for logins mapped to Azure AD users, or type column value set to **X** and type_desc value set to **EXTERNAL_GROUP** for logins mapped to Azure AD groups. - For a script to transfer logins, see [How to transfer the logins and the passwords between instances of SQL Server 2005 and SQL Server 2008](https://support.microsoft.com/kb/918992). - Creating a login automatically enables the new login and grants the login the server level **CONNECT SQL** permission. > [!IMPORTANT] > See [Manage Logins in Azure SQL Database](/azure/sql-database/sql-database-manage-logins) for information about working with logins and users in Azure SQL Database. ## Logins and Permissions Only the server-level principal login (created by the provisioning process) or members of the `securityadmin` or `sysadmin` database role in the master database can create new logins. For more information, see [Server-Level Roles](/azure/sql-database/sql-database-manage-logins#groups-and-roles) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md). By default, the standard permission granted to a newly created Azure AD login in master is: **CONNECT SQL** and **VIEW ANY DATABASE**. ### SQL Managed Instance Logins - Must have **ALTER ANY LOGIN** permission on the server or membership in the one of the fixed server roles `securityadmin` or `sysadmin`. Only an Azure Active Directory (Azure AD) account with **ALTER ANY LOGIN** permission on the server or membership in one of those roles can execute the create command. - If the login is a SQL Principal, only logins that are part of the `sysadmin` role can use the create command to create logins for an Azure AD account. - Must be a member of Azure AD within the same directory used for Azure SQL Managed Instance. ## After creating a login > [!NOTE] > The Azure AD admin for Azure SQL Managed Instance functionality after creation has changed. For more information, see [New Azure AD admin functionality for MI](/azure/sql-database/sql-database-aad-authentication-configure#new-azure-ad-admin-functionality-for-mi). After creating a login, the login can connect to a managed instance, but only has the permissions granted to the **public** role. Consider performing some of the following activities. - To create an Azure AD user from an Azure AD login, see [CREATE USER](../../t-sql/statements/create-user-transact-sql.md). - To grant permissions to a user in a database, use the **ALTER SERVER ROLE** ... **ADD MEMBER** statement to add the user to one of the built-in database roles or a custom role, or grant permissions to the user directly using the [GRANT](../../t-sql/statements/grant-transact-sql.md) statement. For more information, see [Non-administrator Roles](/azure/sql-database/sql-database-manage-logins#non-administrator-users), [Additional server-level administrative roles](/azure/sql-database/sql-database-manage-logins#additional-server-level-administrative-roles), [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md), and [GRANT](grant-transact-sql.md) statement. - To grant server-wide permissions, create a database user in the master database and use the **ALTER SERVER ROLE** ... **ADD MEMBER** statement to add the user to one of the administrative server roles. For more information, see [Server-Level Roles](/azure/sql-database/sql-database-manage-logins#groups-and-roles) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md), and [Server roles](/azure/sql-database/sql-database-manage-logins#additional-server-level-administrative-roles). - Use the following command to add the `sysadmin` role to an Azure AD login: `ALTER SERVER ROLE sysadmin ADD MEMBER [AzureAD_Login_name]` - Use the **GRANT** statement, to grant server-level permissions to the new login or to a role containing the login. For more information, see [GRANT](../../t-sql/statements/grant-transact-sql.md). ## Limitations - Setting an Azure AD login mapped to an Azure AD group as the database owner is not supported. - Impersonation of Azure AD server-level principals using other Azure AD principals is supported, such as the [EXECUTE AS](execute-as-transact-sql.md) clause. - Only SQL server-level principals (logins) that are part of the `sysadmin` role can execute the following operations targeting Azure AD principals: - EXECUTE AS USER - EXECUTE AS LOGIN - External (guest) users imported from another Azure AD directory cannot be directly configured as an Azure AD admin for SQL Managed Instance using the Azure portal. Instead, join external user to an Azure AD security-enabled group and configure the group as the instance administrator. You can use PowerShell or Azure CLI to set individual guest users as the instance administrator. - Login is not replicated to the secondary instance in a failover group. Login is saved in the master database, which is a system database, and as such, is not geo-replicated. To solve this, the user must create login with the same SID on the secondary instance. ```SQL -- Code to create login on the secondary instance CREATE LOGIN foo WITH PASSWORD = '', SID = ; ``` ## Examples ### A. Creating a login with a password The following example creates a login for a particular user and assigns a password. ```sql CREATE LOGIN WITH PASSWORD = ''; GO ``` ### B. Creating a login from a SID The following example first creates a SQL Server authentication login and determines the SID of the login. ```sql CREATE LOGIN TestLogin WITH PASSWORD = 'SuperSecret52&&'; SELECT name, sid FROM sys.sql_logins WHERE name = 'TestLogin'; GO ``` My query returns 0x241C11948AEEB749B0D22646DB1A19F2 as the SID. Your query will return a different value. The following statements delete the login, and then recreate the login. Use the SID from your previous query. ```sql DROP LOGIN TestLogin; GO CREATE LOGIN TestLogin WITH PASSWORD = 'SuperSecret52&&', SID = 0x241C11948AEEB749B0D22646DB1A19F2; SELECT * FROM sys.sql_logins WHERE name = 'TestLogin'; GO ``` ### C. Creating a login for a local Azure AD account The following example creates a login for the Azure AD account joe@myaad.onmicrosoft.com that exists in the Azure AD of *myaad*. ```sql CREATE LOGIN [joe@myaad.onmicrosoft.com] FROM EXTERNAL PROVIDER GO ``` ### D. Creating a login for a federated Azure AD account The following example creates a login for a federated Azure AD account bob@contoso.com that exists in the Azure AD called *contoso*. User bob can also be a guest user. ```sql CREATE LOGIN [bob@contoso.com] FROM EXTERNAL PROVIDER GO ``` ### E. Creating a login for an Azure AD group The following example creates a login for the Azure AD group *mygroup* that exists in the Azure AD of *myaad* ```sql CREATE LOGIN [mygroup] FROM EXTERNAL PROVIDER GO ``` ### F. Creating a login for an Azure AD application The following example creates a login for the Azure AD application *myapp* that exists in the Azure AD of *myaad* ```sql CREATE LOGIN [myapp] FROM EXTERNAL PROVIDER ``` ### G. Check newly added logins To check the newly added login, execute the following T-SQL command: ```sql SELECT * FROM sys.server_principals; GO ``` ## See Also - [Getting Started with Database Engine Permissions](../../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md) - [Principals](../../relational-databases/security/authentication-access/principals-database-engine.md) - [Password Policy](../../relational-databases/security/password-policy.md) - [ALTER LOGIN](../../t-sql/statements/alter-login-transact-sql.md) - [DROP LOGIN](../../t-sql/statements/drop-login-transact-sql.md) - [EVENTDATA](../../t-sql/functions/eventdata-transact-sql.md) - [Create a Login](../../relational-databases/security/authentication-access/create-a-login.md) ::: moniker-end ::: moniker range="=azure-sqldw-latest" :::row::: :::column::: [SQL Server](create-login-transact-sql.md?view=sql-server-ver15&preserve-view=true) :::column-end::: :::column::: [Azure SQL Database](create-login-transact-sql.md?view=azuresqldb-current&preserve-view=true) :::column-end::: :::column::: [Azure SQL
Managed Instance](create-login-transact-sql.md?view=azuresqldb-mi-current&preserve-view=true) :::column-end::: :::column::: **_\* Azure Synapse
Analytics \*_** :::column-end::: :::column::: [Analytics Platform
System (PDW)](create-login-transact-sql.md?view=aps-pdw-2016&preserve-view=true) :::column-end::: :::row-end:::   ## Azure Synapse Analytics ## Syntax ```syntaxsql -- Syntax for Azure Synapse Analytics CREATE LOGIN login_name { WITH } ::= PASSWORD = { 'password' } [ , SID = sid ] ``` ## Arguments *login_name* Specifies the name of the login that is created. SQL Analytics in Azure Synapse supports only SQL logins. To create accounts for Azure Active Directory users, use the [CREATE USER](create-user-transact-sql.md) statement. PASSWORD **='**password**'* Specifies the password for the SQL login that is being created. Use a strong password. For more information, see [Strong Passwords](../../relational-databases/security/strong-passwords.md) and [Password Policy](../../relational-databases/security/password-policy.md). Beginning with [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], stored password information is calculated using SHA-512 of the salted password. Passwords are case-sensitive. Passwords should always be at least eight characters long, and cannot exceed 128 characters. Passwords can include a-z, A-Z, 0-9, and most non-alphanumeric characters. Passwords cannot contain single quotes, or the *login_name*. SID = *sid* Used to recreate a login. Applies to SQL Server authentication logins only, not Windows authentication logins. Specifies the SID of the new SQL Server authentication login. If this option is not used, SQL Server automatically assigns a SID. The SID structure depends on the SQL Server version. For SQL Analytics, this is a 32 byte (**binary(32)**) literal consisting of `0x01060000000000640000000000000000` plus 16 bytes representing a GUID. For example, `SID = 0x0106000000000064000000000000000014585E90117152449347750164BA00A7`. ## Remarks - Passwords are case-sensitive. - For a script to transfer logins, see [How to transfer the logins and the passwords between instances of SQL Server 2005 and SQL Server 2008](https://support.microsoft.com/kb/918992). - Creating a login automatically enables the new login and grants the login the server level **CONNECT SQL** permission. - The server's [authentication mode](../../relational-databases/security/choose-an-authentication-mode.md) must match the login type to permit access. - For information about designing a permissions system, see [Getting Started with Database Engine Permissions](../../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md). ## Logins The **CREATE LOGIN** statement must be the only statement in a batch. When connecting to Azure Synapse using tools such as **sqlcmd**, you must append the SQL Analytics server name to the login name in the connection string by using the *\*@*\* notation. For example, if your login is `login1` and the fully qualified name of the SQL Analytics server is `servername.database.windows.net`, the *username* parameter of the connection string should be `login1@servername`. Because the total length of the *username* parameter is 128 characters, *login_name* is limited to 127 characters minus the length of the server name. In the example, `login_name` can only be 117 characters long because `servername` is 10 characters. To create a login, you must be connected to the master database. SQL Server rules allow you create a SQL Server authentication login in the format \@\. If your [!INCLUDE[ssSDS](../../includes/sssds-md.md)] server is **myazureserver** and your login is **myemail@live.com**, then you must supply your login as **myemail@live.com@myazureserver**. Login data required to authenticate a connection and server-level firewall rules is temporarily cached in each database. This cache is periodically refreshed. To force a refresh of the authentication cache and make sure that a database has the latest version of the logins table, execute [DBCC FLUSHAUTHCACHE](../../t-sql/database-console-commands/dbcc-flushauthcache-transact-sql.md). For more information about logins, see [Managing Databases and Logins](/azure/sql-database/sql-database-manage-logins). ## Permissions Only the server-level principal login (created by the provisioning process) or members of the `loginmanager` database role in the master database can create new logins. For more information, see [Server-Level Roles](/azure/sql-database/sql-database-manage-logins#groups-and-roles) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md). ## After creating a login After creating a login, the login can connect to Azure Synapse but only has the permissions granted to the **public** role. Consider performing some of the following activities. - To connect to a database, create a database user for the login. For more information, see [CREATE USER](../../t-sql/statements/create-user-transact-sql.md). - To grant permissions to a user in a database, use the **ALTER SERVER ROLE** ... **ADD MEMBER** statement to add the user to one of the built-in database roles or a custom role, or grant permissions to the user directly using the [GRANT](grant-transact-sql.md) statement. For more information, see [Non-administrator Roles](/azure/sql-database/sql-database-manage-logins#non-administrator-users), [Additional server-level administrative roles](/azure/sql-database/sql-database-manage-logins#additional-server-level-administrative-roles), [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md), and [GRANT](grant-transact-sql.md) statement. - To grant server-wide permissions, create a database user in the master database and use the **ALTER SERVER ROLE** ... **ADD MEMBER** statement to add the user to one of the administrative server roles. For more information, see [Server-Level Roles](/azure/sql-database/sql-database-manage-logins#groups-and-roles) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md), and [Server roles](/azure/sql-database/sql-database-manage-logins#additional-server-level-administrative-roles). - Use the **GRANT** statement, to grant server-level permissions to the new login or to a role containing the login. For more information, see [GRANT](../../t-sql/statements/grant-transact-sql.md). ## Examples ### A. Creating a login with a password The following example creates a login for a particular user and assigns a password. ```sql CREATE LOGIN WITH PASSWORD = ''; GO ``` ### B. Creating a login from a SID The following example first creates a SQL Server authentication login and determines the SID of the login. ```sql CREATE LOGIN TestLogin WITH PASSWORD = 'SuperSecret52&&'; SELECT name, sid FROM sys.sql_logins WHERE name = 'TestLogin'; GO ``` My query returns 0x241C11948AEEB749B0D22646DB1A19F2 as the SID. Your query will return a different value. The following statements delete the login, and then recreate the login. Use the SID from your previous query. ```sql DROP LOGIN TestLogin; GO CREATE LOGIN TestLogin WITH PASSWORD = 'SuperSecret52&&', SID = 0x241C11948AEEB749B0D22646DB1A19F2; SELECT * FROM sys.sql_logins WHERE name = 'TestLogin'; GO ``` ## See Also - [Getting Started with Database Engine Permissions](../../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md) - [Principals](../../relational-databases/security/authentication-access/principals-database-engine.md) - [Password Policy](../../relational-databases/security/password-policy.md) - [ALTER LOGIN](../../t-sql/statements/alter-login-transact-sql.md) - [DROP LOGIN](../../t-sql/statements/drop-login-transact-sql.md) - [EVENTDATA](../../t-sql/functions/eventdata-transact-sql.md) - [Create a Login](../../relational-databases/security/authentication-access/create-a-login.md) ::: moniker-end ::: moniker range=">=aps-pdw-2016" :::row::: :::column::: [SQL Server](create-login-transact-sql.md?view=sql-server-ver15&preserve-view=true) :::column-end::: :::column::: [Azure SQL Database](create-login-transact-sql.md?view=azuresqldb-current&preserve-view=true) :::column-end::: :::column::: [Azure SQL
Managed Instance](create-login-transact-sql.md?view=azuresqldb-mi-current&preserve-view=true) :::column-end::: :::column::: [Azure Synapse
Analytics](create-login-transact-sql.md?view=azure-sqldw-latest&preserve-view=true) :::column-end::: :::column::: **_\* Analytics
Platform System (PDW) \*_** :::column-end::: :::row-end:::   ## Analytics Platform System ## Syntax ```syntaxsql -- Syntax for Analytics Platform System CREATE LOGIN loginName { WITH | FROM WINDOWS } ::= PASSWORD = { 'password' } [ MUST_CHANGE ] [ , [ ,... ] ] ::= CHECK_EXPIRATION = { ON | OFF} | CHECK_POLICY = { ON | OFF} ``` ## Arguments *login_name* Specifies the name of the login that is created. There are four types of logins: SQL Server logins, Windows logins, certificate-mapped logins, and asymmetric key-mapped logins. When you are creating logins that are mapped from a Windows domain account, you must use the pre-Windows 2000 user logon name in the format [\\\]. You cannot use a UPN in the format login_name@DomainName. For an example, see example D later in this article. Authentication logins are type **sysname** and must conform to the rules for [Identifiers](../../relational-databases/databases/database-identifiers.md) and cannot contain a '**\\**'. Windows logins can contain a '**\\**'. Logins based on Active Directory users, are limited to names of fewer than 21 characters. PASSWORD **='**_password_' Applies to SQL Server logins only. Specifies the password for the login that is being created. Use a strong password. For more information, see [Strong Passwords](../../relational-databases/security/strong-passwords.md) and [Password Policy](../../relational-databases/security/password-policy.md). Beginning with SQL Server 2012 (11.x), stored password information is calculated using SHA-512 of the salted password. Passwords are case-sensitive. Passwords should always be at least eight characters long, and cannot exceed 128 characters. Passwords can include a-z, A-Z, 0-9, and most non-alphanumeric characters. Passwords cannot contain single quotes, or the *login_name*. MUST_CHANGE Applies to SQL Server logins only. If this option is included, SQL Server prompts the user for a new password the first time the new login is used. CHECK_EXPIRATION **=** { ON | **OFF** } Applies to SQL Server logins only. Specifies whether password expiration policy should be enforced on this login. The default value is OFF. CHECK_POLICY **=** { **ON** | OFF } Applies to SQL Server logins only. Specifies that the Windows password policies of the computer on which SQL Server is running should be enforced on this login. The default value is ON. If the Windows policy requires strong passwords, passwords must contain at least three of the following four characteristics: - An uppercase character (A-Z). - A lowercase character (a-z). - A digit (0-9). - One of the non-alphanumeric characters, such as a space, _, @, *, ^, %, !, $, #, or &. WINDOWS Specifies that the login be mapped to a Windows login. ## Remarks - Passwords are case-sensitive. - If MUST_CHANGE is specified, CHECK_EXPIRATION and CHECK_POLICY must be set to ON. Otherwise, the statement will fail. - A combination of CHECK_POLICY = OFF and CHECK_EXPIRATION = ON is not supported. - When CHECK_POLICY is set to OFF, *lockout_time* is reset and CHECK_EXPIRATION is set to OFF. > [!IMPORTANT] > CHECK_EXPIRATION and CHECK_POLICY are only enforced on Windows Server 2003 and later. For more information, see [Password Policy](../../relational-databases/security/password-policy.md). - For a script to transfer logins, see [How to transfer the logins and the passwords between instances of SQL Server 2005 and SQL Server 2008](https://support.microsoft.com/kb/918992). - Creating a login automatically enables the new login and grants the login the server level **CONNECT SQL** permission. - For information about designing a permissions system, see [Getting Started with Database Engine Permissions](../../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md). ## Permissions Only users with **ALTER ANY LOGIN** permission on the server or membership in the **securityadmin** fixed server role can create logins. For more information, see [Server-Level Roles](/azure/sql-database/sql-database-manage-logins#groups-and-roles) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md). ## After creating a login After creating a login, the login can connect to Azure Synapse Analytics, but only has the permissions granted to the **public** role. Consider performing some of the following activities. - To connect to a database, create a database user for the login. For more information, see [CREATE USER](../../t-sql/statements/create-user-transact-sql.md). - Create a user-defined server role by using [CREATE SERVER ROLE](../../t-sql/statements/create-server-role-transact-sql.md). Use **ALTER SERVER ROLE** ... **ADD MEMBER** to add the new login to the user-defined server role. For more information, see [CREATE SERVER ROLE](../../t-sql/statements/create-server-role-transact-sql.md) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md). - Use **sp_addsrvrolemember** to add the login to a fixed server role. For more information, see [Server-Level Roles](../../relational-databases/security/authentication-access/server-level-roles.md) and [sp_addsrvrolemember](../../relational-databases/system-stored-procedures/sp-addsrvrolemember-transact-sql.md). - Use the **GRANT** statement, to grant server-level permissions to the new login or to a role containing the login. For more information, see [GRANT](../../t-sql/statements/grant-transact-sql.md). ## Examples ### G. Creating a SQL Server authentication login with a password The following example creates the login `Mary7` with password `A2c3456`. ```sql CREATE LOGIN Mary7 WITH PASSWORD = 'A2c3456$#' ; ``` ### H. Using Options The following example creates the login `Mary8` with password and some of the optional arguments. ```sql CREATE LOGIN Mary8 WITH PASSWORD = 'A2c3456$#' MUST_CHANGE, CHECK_EXPIRATION = ON, CHECK_POLICY = ON; ``` ### I. Creating a login from a Windows domain account The following example creates a login from a Windows domain account named `Mary` in the `Contoso` domain. ```sql CREATE LOGIN [Contoso\Mary] FROM WINDOWS; GO ``` ## See Also - [Getting Started with Database Engine Permissions](../../relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md) - [Principals](../../relational-databases/security/authentication-access/principals-database-engine.md) - [Password Policy](../../relational-databases/security/password-policy.md) - [ALTER LOGIN](../../t-sql/statements/alter-login-transact-sql.md) - [DROP LOGIN](../../t-sql/statements/drop-login-transact-sql.md) - [EVENTDATA](../../t-sql/functions/eventdata-transact-sql.md) - [Create a Login](../../relational-databases/security/authentication-access/create-a-login.md) --- ::: moniker-end