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/azure-data-studio/quickstart-sql-database.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
@@ -33,7 +33,7 @@ Use Azure Data Studio to establish a connection to your Azure SQL Database serve
33
33
34
34
1. The first time you run Azure Data Studio the **Welcome** page should open. If you don't see the **Welcome** page, select **Help** > **Welcome**. Select **New Connection** to open the **Connection** pane:

37
37
38
38
2. This article uses SQL sign-in, but also supports Windows authentication. Fill in the following fields using the server name, user name, and password for your Azure SQL server:
39
39
@@ -47,7 +47,7 @@ Use Azure Data Studio to establish a connection to your Azure SQL Database serve
47
47
|**Database name**|*leave blank*| You're only connecting to the server here. |
48
48
|**Server Group**| Select <Default> | You can set this field to a specific server group you created. |
Copy file name to clipboardExpand all lines: docs/azure-data-studio/quickstart-sql-dw.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Use Azure Data Studio to establish a connection to your Azure Synapse Analytics
31
31
32
32
1. The first time you run Azure Data Studio the **Connection** page should open. If you don't see the **Connection** page, select **Add Connection**, or the **New Connection** icon in the **SERVERS** sidebar:

35
35
36
36
2. This article uses *SQL Login*, but *Windows Authentication* is also supported. Fill in the fields as follows using the server name, user name, and password for *your* Azure SQL server:
Copy file name to clipboardExpand all lines: docs/azure-data-studio/tutorial-table-space-sql-server.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
@@ -39,7 +39,7 @@ Azure Data Studio has a built-in sample widget to monitor the space used by tabl
39
39
40
40
4. To customize the **dashboard.database.widgets** settings, you need to edit the **dashboard.database.widgets** entry in the **USER SETTINGS** section.

43
43
44
44
If there is no **dashboard.database.widgets** in the **USER SETTINGS** section, hover over the **dashboard.database.widgets** text in the DEFAULT SETTINGS column and click the *gear* icon that appears to the left of the text and click **Copy as Setting JSON**. If the pop-up says **Replace in Settings**, don't click it! Go to the **USER SETTINGS** column to the right and locate the **dashboard.database.widgets** section and advance to the next step.
45
45
@@ -60,7 +60,7 @@ Azure Data Studio has a built-in sample widget to monitor the space used by tabl
60
60
61
61
The **dashboard.database.widgets** section should look similar to the following image:

Copy file name to clipboardExpand all lines: docs/connect/ado-net/step-1-configure-development-environment-ado-net-development.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
@@ -24,7 +24,7 @@ Our current code example uses ADO.NET of the .NET Framework, for Windows. The .N
24
24
25
25
### ADO.NET, for Windows
26
26
27
-
-[To download and install .NET Framework, including ADO.NET](../sql-connection-libraries.md#anchor-20-drivers-relational-access)
27
+
-:::image type="icon" source="../../ssms/media/download-icon.png"::: [To download and install .NET Framework, including ADO.NET](../sql-connection-libraries.md#anchor-20-drivers-relational-access)
28
28
29
29
- Install Visual Studio Community, or a similar integrated development environment (IDE) for writing and compiling C# source code. Microsoft now provides Visual Studio Community for *free*.
30
30
-[Download Visual Studio Community](https://www.visualstudio.com/products/visual-studio-community-vs)
@@ -35,4 +35,4 @@ Our current code example uses ADO.NET of the .NET Framework, for Windows. The .N
35
35
36
36
Links to download .NET Core, for a variety of operating systems, are available at:
37
37
38
-
-[To download and install .NET Core](../sql-connection-libraries.md#anchor-20-drivers-relational-access)
38
+
-:::image type="icon" source="../../ssms/media/download-icon.png"::: [To download and install .NET Core](../sql-connection-libraries.md#anchor-20-drivers-relational-access)

54
54
55
55
## Add sources to assess
56
56
57
57
1. Select the SSIS package storage types to assess, and then select **Add**.
Copy file name to clipboardExpand all lines: docs/includes/create-workload-group.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
Creates a Resource Governor workload group and associates the workload group with a Resource Governor resource pool. Resource Governor is not available in every edition of [!INCLUDE[msCoName](msconame-md.md)][!INCLUDE[ssNoVersion](ssnoversion-md.md)]. For a list of features that are supported by the editions of [!INCLUDE[ssNoVersion](ssnoversion-md.md)], see [Features Supported by the Editions of SQL Server 2016](~/sql-server/editions-and-supported-features-for-sql-server-2016.md).
2
2
3
-
[Transact-SQL Syntax Conventions](../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md).
Copy file name to clipboardExpand all lines: docs/includes/drop-workload-group.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
Drops an existing user-defined Resource Governor workload group.
2
2
3
-
[Transact-SQL Syntax Conventions](../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md).
Copy file name to clipboardExpand all lines: docs/includes/sql-server-ha-story.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,7 @@ One of the benefits of availability groups is that both high availability and di
148
148
Outside of an availability group with a cluster type of none, an availability group requires that all replicas are part of the same underlying cluster whether it is a WSFC or Pacemaker. This means that in the picture above, the WSFC is stretched to work in two different data centers which adds complexity. regardless of the platform (Windows Server or Linux). Stretching clusters across distance adds complexity.
149
149
Introduced in SQL Server 2016, a distributed availability group allows an availability group to span availability groups configured on different clusters. This decouples the requirement to have the nodes all participate in the same cluster, which makes configuring disaster recovery much easier. For more information on distributed availability groups, see [Distributed availability groups](../database-engine/availability-groups/windows/distributed-availability-groups.md).

152
152
153
153
### Always on failover cluster instances
154
154
@@ -218,7 +218,7 @@ Before covering the cross-platform and interoperability scenarios, two facts nee
218
218
219
219
Distributed availability groups are designed to span availability group configurations, whether those two underlying clusters underneath the availability groups are two different WSFCs, Linux distributions, or one on a WSFC and the other on Linux. A distributed availability group will be the primary method of having a cross platform solution. A distributed availability group is also the primary solution for migrations such as converting from a Windows Server-based SQL Server infrastructure to a Linux-based one if that is what your company wants to do. As noted above, availability groups, and especially distributed availability groups, would minimize the time that an application would be unavailable for use. An example of a distributed availability group that spans a WSFC and Pacemaker is shown below.

222
222
223
223
If an availability group is configured with a cluster type of None, it can span Windows Server and Linux as well as multiple Linux distributions. Since this is not a true high availability configuration, it should not be used for mission critical deployments, but for read-scale or migration/upgrade scenarios.
224
224
@@ -235,7 +235,7 @@ Since their introduction in SQL Server 2012, secondary replicas have had the abi
235
235
236
236
Scaling readable copies of a database via availability groups was first introduced with distributed availability groups in SQL Server 2016. This would allow companies to have read-only copies of the database not only locally, but regionally and globally with a minimal amount of configuration and reduce network traffic and latency by having queries executed locally. Each primary replica of an availability group can seed two other availability groups even if it is not the fully read/write copy, so each distributed availability group can support up to 27 copies of the data that are readable.

239
239
240
240
Starting with SQL Server 2017, It is possible to create a near-real time, read-only solution with availability groups configured with a cluster type of None. If the goal is to use availability groups for readable secondary replicas and not availability, doing this removes the complexity of using a WSFC or Pacemaker, and gives the readable benefits of an availability group in a simpler deployment method.
Copy file name to clipboardExpand all lines: docs/integration-services/import-export-data/performing-operation-sql-server-import-and-export-wizard.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ After you review the choices that you made in the wizard and click **Finish** on
28
28
## Screen shot - Operation completed
29
29
The following screen shot shows the **Performing Operation** page of the wizard after the operation is complete. Click on an item in the **Message** column to get more info about the corresponding step.
30
30
31
-

31
+

0 commit comments