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: azure-sql/database-watcher-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: An overview of database watcher for Azure SQL, a managed monitoring
5
5
author: lcwright
6
6
ms.author: lancewright
7
7
ms.reviewer: wiassaf, dfurman
8
-
ms.date: 05/05/2025
8
+
ms.date: 06/04/2025
9
9
ms.service: azure-sql
10
10
ms.subservice: monitoring
11
11
ms.topic: conceptual
@@ -289,7 +289,7 @@ To validate that you have access and can connect to the data store, and that the
289
289
The database watcher team at Microsoft is looking forward to your comments and suggestions. You can send product feedback in one of the following ways:
290
290
291
291
- Post a new idea in the [SQL feedback forum](https://aka.ms/sqlfeedback). On the **Post a new idea** page, use **SQL** as the forum, select the **Azure SQL** group, and include *database watcher* in the title. The feedback you submit in the feedback forum is public. Other community members can upvote and comment on your ideas and suggestions. Community votes and comments help the database watcher team plan and prioritize product improvements.
292
-
- Use the feedback button on one of database watcher pages in the Azure portal. For example, you can find the feedback button on the watcher **Overview** page, or on dashboards next to the refresh button. The feedback you send this way is not public. When you submit feedback, you can optionally allow Microsoft to email you regarding this feedback for follow-ups and clarifications.
292
+
- Use the feedback button on one of database watcher pages in the Azure portal. For example, you can find the feedback button on the watcher **Overview** page, or on dashboards next to the refresh button. The feedback you send this way is not public. While Microsoft will see your feedback, depending on your preference and the privacy rules in effect, Microsoft might not be able to respond to you regarding this feedback.
293
293
294
294
For technical support or help solving a problem with database watcher, [open a support case](https://azure.microsoft.com/support/create-ticket/).
Copy file name to clipboardExpand all lines: azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Cloud Business Continuity - Disaster Recovery
3
3
titleSuffix: Azure SQL Database
4
-
description: Learn how Azure SQL Database supports cloud business continuity and disaster recovery to help keep mission-critical cloud applications running.
4
+
description: Learn what to do when a user or application error affects data integrity, an Azure availability zone or region has an outage, or your application requires maintenance.
This article provides an overview of the business continuity and disaster recovery capabilities of Azure SQL Database, describing the options and recommendations to recover from disruptive events that could lead to data loss or cause your database and application to become unavailable. Learn what to do when a user or application error affects data integrity, an Azure availability zone or region has an outage, or your application requires maintenance.
31
+
**Business continuity** in Azure SQL Database refers to the mechanisms, policies, and procedures that enable your business to continue operating in the face of disruption by providing availability, high availability, and disaster recovery.
For prescriptive recommendations to maximize availability and achieve higher business continuity, see:
36
38
37
-
**Business continuity** in Azure SQL Database refers to the mechanisms, policies, and procedures that enable your business to continue operating in the face of disruption by providing availability, high availability, and disaster recovery.
In most cases, SQL Database handles disruptive events that might happen in a cloud environment and keeps your applications and business processes running. However, there are some disruptive events where mitigation might take some time, such as:
40
44
@@ -43,12 +47,6 @@ In most cases, SQL Database handles disruptive events that might happen in a clo
43
47
- Catastrophic natural disaster event takes down a datacenter or availability zone or region.
44
48
- Rare datacenter, availability zone, or region-wide outage caused by a configuration change, software bug, or hardware failure.
45
49
46
-
For prescriptive recommendations to maximize availability and achieve higher business continuity, see:
Azure SQL Database comes with a core resiliency and reliability promise that protects it against software or hardware failures. Database backups are automated to protect your data from corruption or accidental deletion. As a Platform-as-a-service (PaaS), the Azure SQL Database service provides availability as an off-the-shelf feature with an industry-leading availability SLA of 99.99%.
Copy file name to clipboardExpand all lines: docs/connect/odbc/windows/odbc-administrator-dsn-creation.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,10 @@
1
1
---
2
-
title: ODBC Data Source Administrator DSN options
2
+
title: ODBC Data Source Administrator DSN Options
3
3
description: This article describes the options available when creating a new DSN connection to SQL Server using the ODBC Data Source Administrator application.
4
4
author: David-Engel
5
5
ms.author: davidengel
6
-
ms.date: "03/29/2024"
6
+
ms.reviewer: randolphwest
7
+
ms.date: 06/05/2025
7
8
ms.service: sql
8
9
ms.subservice: connectivity
9
10
ms.topic: conceptual
@@ -14,11 +15,11 @@ This article describes the options available when creating a new DSN connection
14
15
15
16
When you create a DSN, the wizard displays a series of screens that allow you to specify the information needed to connect to SQL Server.
16
17
17
-
## Create New Data Source
18
+
## Create new data source
18
19
19
20
This article only pertains to creating a DSN using the ODBC driver for SQL Server. The ODBC Data Source Administrator dialog box is displayed when you select **Add** in the **User DSN**, **System DSN**, or **File DSN** tab of the ODBC Data Source Administrator dialog box. Choose the driver and select **Finish** to display the first screen of the wizard.
20
21
21
-
## Create a New Data Source to SQL Server - Screen 1
22
+
## Create a new data source to SQL Server - Screen 1
22
23
23
24
### Name
24
25
@@ -34,15 +35,15 @@ The name of an instance of SQL Server on your network. You'll need to specify a
34
35
35
36
In most cases, the ODBC driver can connect by using the default protocol order and the server name supplied in this box. Use SQL Server Configuration Manager if you want to create an alias for the server or configure client network libraries.
36
37
37
-
You can enter "(local)" in the server box when you're using the same computer as SQL Server. The user can then connect to the local instance of SQL Server, even when running a non-networked version of SQL Server. Multiple instances of SQL Server can run on the same computer. To specify a named instance of SQL Server, the server name is specified as _ServerName_\\_InstanceName_.
38
+
You can enter "(local)" in the server box when you're using the same computer as SQL Server. The user can then connect to the local instance of SQL Server, even when running a non-networked version of SQL Server. Multiple instances of SQL Server can run on the same computer. To specify a named instance of SQL Server, the server name is specified as `<ServerName>\<InstanceName>`.
38
39
39
-
For more information about server names for different types of networks, see [Logging In to SQL Server](../../../database-engine/configure-windows/logging-in-to-sql-server.md#format-for-specifying-the-name-of-sql-server).
40
+
For more information about server names for different types of networks, see [Sign in to SQL Server](../../../database-engine/configure-windows/logging-in-to-sql-server.md#format-for-specifying-the-instance-name).
40
41
41
42
### Finish (optional)
42
43
43
44
If the information specified on this screen is all that is needed to connect to SQL Server, you can select **Finish**. Defaults are used for all attributes specified on other screens of the wizard.
44
45
45
-
## Create a New Data Source to SQL Server - Screen 2
46
+
## Create a new data source to SQL Server - Screen 2
46
47
47
48
Specify the method of authentication, and set up Microsoft SQL Server advanced-client entries and the login and password the ODBC driver for SQL Server will use to connect to SQL Server while configuring the data source.
48
49
@@ -88,7 +89,7 @@ Specifies the password the driver uses when connecting to SQL Server if **With S
88
89
89
90
Both the **Login ID** and **Password** boxes are disabled if **With Integrated Windows authentication** or **With Active Directory Integrated authentication** is selected.
90
91
91
-
## Create a New Data Source to SQL Server - Screen 3
92
+
## Create a new data source to SQL Server - Screen 3
92
93
93
94
Specify the default database, various ANSI options to be used by the driver, and the name of a mirror server.
94
95
@@ -115,42 +116,42 @@ Specifies that `QUOTED_IDENTIFIER` is set to on when the ODBC driver for SQL Ser
115
116
```sql
116
117
SELECT"LastName"
117
118
FROM"Person.Contact"
118
-
WHERE"LastName"='O''Brien'
119
+
WHERE"LastName"='O''Brien';
119
120
```
120
121
121
122
When this check box is cleared, applications that use quoted identifiers, such as the Microsoft Query utility that comes with Microsoft Excel, encounter errors when they generate SQL statements with quoted identifiers.
122
123
123
124
### Use ANSI nulls, paddings, and warnings
124
125
125
-
Specifies that the ANSI_NULLS, ANSI_WARNINGS, and ANSI_PADDINGS options be set on when the ODBC Driver for SQL Server connects.
126
+
Specifies that the `ANSI_NULLS`, `ANSI_WARNINGS`, and `ANSI_PADDINGS` options be set on when the ODBC Driver for SQL Server connects.
126
127
127
-
With ANSI_NULLS set on, the server enforces ANSI rules regarding comparing columns for NULL. The ANSI syntax "IS NULL" or "IS NOT NULL" must be used for all NULL comparisons. The Transact-SQL syntax "= NULL" isn't supported.
128
+
With `ANSI_NULLS` set on, the server enforces ANSI rules regarding comparing columns for `NULL`. The ANSI syntax `IS NULL` or `IS NOT NULL` must be used for all `NULL` comparisons. The Transact-SQL syntax `= NULL` isn't supported.
128
129
129
-
With ANSI_WARNINGS set on, SQL Server issues warning messages for conditions that violate ANSI rules but don't violate the rules of Transact-SQL. Examples of such errors are data truncation on execution of an INSERT or UPDATE statement, or encountering a null value during an aggregate function.
130
+
With `ANSI_WARNINGS` set on, SQL Server issues warning messages for conditions that violate ANSI rules but don't violate the rules of Transact-SQL. Examples of such errors are data truncation on execution of an `INSERT` or `UPDATE` statement, or encountering a null value during an aggregate function.
130
131
131
-
With ANSI_PADDING set on, trailing blanks on **varchar** values and trailing zeroes on **varbinary** values aren't automatically trimmed.
132
+
With `ANSI_PADDING` set on, trailing blanks on **varchar** values and trailing zeroes on **varbinary** values aren't automatically trimmed.
132
133
133
134
### Application intent
134
135
135
136
Declares the application workload type when connecting to a server. Possible values are **ReadOnly** and **ReadWrite**.
136
137
137
138
### Multi-subnet failover
138
139
139
-
If your application is connecting to a high-availability, disaster recovery (Always On Availability Groups) availability group (AG) on different subnets, enabling **Multi-subnet failover** configures ODBC Driver for SQL Server to provide faster detection of and connection to the (currently) active server.
140
+
If your application is connecting to an availability group (AG) on different subnets, enabling **Multi-subnet failover** configures ODBC Driver for SQL Server to provide faster detection of and connection to the (currently) active server.
140
141
141
-
### Transparent Network IP Resolution
142
+
### Transparent network IP resolution
142
143
143
-
Alters the behavior of **Multi-subnet failover** to allow for faster reconnection during failover. For more information, see [Using Transparent Network IP Resolution](../using-transparent-network-ip-resolution.md).
144
+
Alters the behavior of **Multi-subnet failover** to allow for faster reconnection during failover. For more information, see [Using Transparent Network IP Resolution with the ODBC Driver](../using-transparent-network-ip-resolution.md).
144
145
145
-
### Column Encryption
146
+
### Column encryption
146
147
147
148
Enables automatic decryption and encryption of data transfers to and from columns encrypted with the [Always Encrypted](../using-always-encrypted-with-the-odbc-driver.md) feature available in SQL Server 2016 and later.
148
149
149
150
### Use FMTONLY metadata discovery
150
151
151
152
Use the legacy SET FMTONLY metadata discovery method when connecting to SQL Server 2012 or newer. Enable this option only when using queries not supported by [sp_describe_first_result_set](../../../relational-databases/system-stored-procedures/sp-describe-first-result-set-transact-sql.md), such as those containing temporary tables.
152
153
153
-
## Create a New Data Source to SQL Server - Screen 4
154
+
## Create a new data source to SQL Server - Screen 4
154
155
155
156
Specify the language to be used for SQL Server messages, the character set translation, and whether the ODBC driver for SQL Server should use regional settings. You can also control the logging of long-running queries and driver statistics settings.
156
157
@@ -208,12 +209,12 @@ Specifies the number of times to retry an unsuccessful connection attempt.
208
209
209
210
### Connect retry interval (seconds)
210
211
211
-
Specifies the number of seconds between each connection retry attempt. For more information on the operation of this option and the **Connect retry count** options, see [Connection Resiliency](../connection-resiliency.md).
212
+
Specifies the number of seconds between each connection retry attempt. For more information on the operation of this option and the **Connect retry count** options, see [Connection resiliency in the ODBC driver](../connection-resiliency.md).
212
213
213
214
### Finish
214
215
215
216
If the information specified on this screen is complete, you can select **Finish**. The DSN is created using all attributes specified on this and other screens of the wizard, and you're given an opportunity to test the newly created DSN.
216
217
217
218
## Related content
218
219
219
-
[Microsoft ODBC Driver for SQL Server on Windows](../../../connect/odbc/windows/microsoft-odbc-driver-for-sql-server-on-windows.md)
220
+
-[Microsoft ODBC Driver for SQL Server on Windows](microsoft-odbc-driver-for-sql-server-on-windows.md)
Copy file name to clipboardExpand all lines: docs/database-engine/configure-windows/configure-the-remote-access-server-configuration-option.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: "Server configuration: remote access"
2
+
title: "Server Configuration: remote access"
3
3
description: Learn about alternatives to the deprecated remote access option. View other sources for troubleshooting issues with SQL Server connections.
4
4
author: rwestMSFT
5
5
ms.author: randolphwest
6
-
ms.date: 05/19/2025
6
+
ms.date: 06/05/2025
7
7
ms.service: sql
8
8
ms.subservice: configuration
9
9
ms.topic: conceptual
@@ -16,15 +16,17 @@ helpviewer_keywords:
16
16
17
17
This article is about the `remote access` configuration option, which is a deprecated [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] communication feature.
18
18
19
+
For information about linked servers, see [Linked Servers (Database Engine)](../../relational-databases/linked-servers/linked-servers-database-engine.md).
20
+
19
21
This option affects servers that are added by using [sp_addserver](../../relational-databases/system-stored-procedures/sp-addserver-transact-sql.md) and [sp_addlinkedserver](../../relational-databases/system-stored-procedures/sp-addlinkedserver-transact-sql.md). You should leave `remote access` enabled (the default) if you use [linked servers](../../relational-databases/linked-servers/linked-servers-database-engine.md).
If you reached this page because you're having trouble connecting to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], see one of the following articles instead:
25
27
26
-
-[Tutorial: Getting started with the Database Engine](../../relational-databases/tutorial-getting-started-with-the-database-engine.md)
27
-
-[Logging in to SQL Server](logging-in-to-sql-server.md)
28
+
-[Tutorial: Get started with the Database Engine](../../relational-databases/tutorial-getting-started-with-the-database-engine.md)
29
+
-[Sign in to SQL Server](logging-in-to-sql-server.md)
28
30
-[Connect to SQL Server when system administrators are locked out](connect-to-sql-server-when-system-administrators-are-locked-out.md)
29
31
-[Connect to a registered server (SQL Server Management Studio)](../../ssms/register-servers/connect-to-a-registered-server-sql-server-management-studio.md)
30
32
-[Connect to any SQL Server component from SQL Server Management Studio](../../ssms/f1-help/connect-to-any-sql-server-component-from-sql-server-management-studio.md)
@@ -84,6 +86,7 @@ For more information, see [Server configuration options](server-configuration-op
0 commit comments