You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/connect/odbc/windows/sql-server-login-dialog.md
+25-22Lines changed: 25 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,41 +4,40 @@ description: "The SQL Server Login dialog may appear when an application makes a
4
4
author: David-Engel
5
5
ms.author: davidengel
6
6
ms.reviewer: v-davidengel
7
-
ms.date: "03/29/2024"
7
+
ms.date: 12/11/2025
8
8
ms.service: sql
9
9
ms.subservice: connectivity
10
-
ms.topic: conceptual
10
+
ms.topic: concept-article
11
11
---
12
-
# SQL Server Login Dialog Box (ODBC)
12
+
# SQL Server Login dialog box (ODBC)
13
13
14
14
When you call an ODBC connection without specifying enough information for the driver to connect to a SQL Server, the ODBC driver displays the **SQL Server Login** dialog box.
15
15
16
16
## Options
17
17
18
18
### Server
19
19
20
-
The name of an instance of SQL Server on your network. Select a server\instance name from the list, or type the server\instance name in the **Server** box. Optionally, you can create a server alias on the client computer using **SQL Server Configuration Manager**, and type that name in the **Server** box.
20
+
The name of an instance of SQL Server on your network. Select a server\instance name from the list, or type the `<server>\<instance>` name in the **Server** box. Optionally, you can create a server alias on the client computer using **SQL Server Configuration Manager**, and type that name in the **Server** box.
21
21
22
-
You can enter "(local)" when you are using the same computer as SQL Server. You can then connect to a local instance of SQL Server, even when running a non-networked version of SQL Server.
22
+
You can enter `(local)` when you're using the same computer as SQL Server. You can then connect to a local instance of SQL Server, even when running a non-networked version of SQL Server.
23
23
24
24
For more information about server names for different types of networks, see the SQL Server installation documentation in SQL Server Books Online.
25
25
26
26
### Authentication Mode
27
27
28
-
Selects the authentication mode from one of the following:
28
+
You can select the following authentication options from the dropdown list:
29
29
30
-
-**SQL Server** with login ID and password
31
-
-**Windows Integrated** authentication using the currently logged-in user's account
32
-
-**Active Directory Password** with login ID and password
33
-
-**Active Directory Integrated** authentication using the currently logged-in Microsoft Entra user's account
30
+
| Value | Description |
31
+
| --- | --- |
32
+
|**SQL Server**| Authenticate using SQL username and password. |
33
+
|**Windows Integrated**| Authenticate to SQL Server using the currently logged-in user's Windows account credentials. |
34
+
|**Active Directory Password**| Username and password authentication with a Microsoft Entra identity. |
35
+
|**Active Directory Integrated**| Integrated Windows authentication through Microsoft Entra ID. This mode is used for Windows authentication in Active Directory environments federated with Microsoft Entra ID. |
36
+
|**Active Directory Interactive**| Interactive authentication with a Microsoft Entra identity. This mode supports Microsoft Entra multifactor authentication. |
37
+
|**Managed Service Identity**| Authenticate with a Microsoft Entra managed identity. |
38
+
|**Active Directory Service Principal**| Authentication with a Microsoft Entra service principal. **Login ID** should be set to the application (client) ID. **Password** should be set to the application (client) secret. |
34
39
35
-
-**Active Directory Interactive** authentication with a Microsoft Entra login ID
36
-
37
-
-**Managed Service Identity** authentication with Microsoft Entra managed identity
38
-
39
-
-**Active Directory Service Principal** authentication with a Microsoft Entra service principal
40
-
41
-
See [ODBC Data Source Administrator DSN options](odbc-administrator-dsn-creation.md) for more information on the authentication modes.
40
+
For more information about authentication modes, see [ODBC Data Source Administrator DSN options](odbc-administrator-dsn-creation.md).
42
41
43
42
### Server SPN
44
43
@@ -86,11 +85,11 @@ Specifies the national language to use for SQL Server system messages. The compu
86
85
87
86
### Application Name
88
87
89
-
(Optional) Specifies the application name to be stored in the **program_name** column in the row for this connection in **sys.sysprocesses**.
88
+
(Optional) Specifies the application name to be stored in the `program_name` column in the row for this connection in `sys.sysprocesses`.
90
89
91
90
### Workstation ID
92
91
93
-
(Optional) Specifies the workstation ID to be stored in the **hostname** column in the row for this connection in **sys.sysprocesses**.
92
+
(Optional) Specifies the workstation ID to be stored in the `hostname` column in the row for this connection in `sys.sysprocesses`.
94
93
95
94
### Use strong encryption for data
96
95
@@ -102,16 +101,20 @@ Declares the connection encryption mode to be used. Selecting the **Optional** o
102
101
103
102
### Server certificate (optional)
104
103
105
-
Specifies the server certificate (PEM, DER, or CER format) to match against the certificate returned by the server during encryption negotiation. When specified, certificate validation is done by checking if the server's certificate is an exact match against the certificate specified. The **Hostname in certificate** option is ignored when a server certificate is specified. This option is applicable only when **Connection Encryption** is set to **Strict** and is available in ODBC Driver 18.1 and newer.
104
+
Specifies the server certificate (PEM, DER, or CER format) to match against the certificate returned by the server during encryption negotiation. When specified, certificate validation is done by checking if the server's certificate is an exact match against the certificate specified.
105
+
106
+
The **Hostname in certificate** option is ignored when a server certificate is specified. This option is applicable only when **Connection Encryption** is set to **Strict** and is available in ODBC Driver 18.1 and newer.
106
107
107
108
### Hostname in certificate (optional)
108
109
109
110
Specifies the hostname to be used when validating the server's certificate. When left blank, the server name is used as the hostname for validation. A hostname can only be specified when **Trust server certificate** is unselected. This option is available in ODBC Driver 18 and newer.
110
111
111
112
### Trust server certificate
112
113
113
-
This option is applicable only when **Use strong encryption for data** is enabled (ODBC Driver 17 and older), or when **Connection Encryption** is set to **Optional** or **Mandatory** (ODBC Driver 18 and newer). When selected, the server's certificate won't be validated to have the correct hostname of the server and be issued by a trusted certificate authority. The server's certificate will always be validated when using the **Strict** encryption mode.
114
+
This option is applicable only when **Use strong encryption for data** is enabled (ODBC Driver 17 and older), or when **Connection Encryption** is set to **Optional** or **Mandatory** (ODBC Driver 18 and newer).
115
+
116
+
When selected, the server's certificate won't be validated to have the correct hostname of the server and be issued by a trusted certificate authority. The server's certificate will always be validated when using the **Strict** encryption mode.
114
117
115
118
## Related content
116
119
117
-
[Microsoft ODBC Driver for SQL Server on Windows](../../../connect/odbc/windows/microsoft-odbc-driver-for-sql-server-on-windows.md)
120
+
-[Microsoft ODBC Driver for SQL Server on Windows](microsoft-odbc-driver-for-sql-server-on-windows.md)
0 commit comments