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: articles/azure-sql/database/data-sync-sql-server-configure.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,22 +29,22 @@ For PowerShell examples on how to configure SQL Data Sync, see [How to sync betw
29
29
30
30
1. Go to the [Azure portal](https://portal.azure.com) to find your SQL database. Search for and select **SQL databases**.
31
31
32
-

32
+

33
33
34
34
1. Select the database you want to use as the hub database for Data Sync.
35
35
36
-

36
+

37
37
38
38
> [!NOTE]
39
39
> The hub database is a sync topology's central endpoint, in which a sync group has multiple database endpoints. All other member databases with endpoints in the sync group, sync with the hub database.
40
40
41
41
1. On the **SQL database** menu for the selected database, select **Sync to other databases**.
42
42
43
-

43
+

44
44
45
45
1. On the **Sync to other databases** page, select **New Sync Group**. The **New sync group** page opens with **Create sync group (step 1)** highlighted.
On the **Create Data Sync Group** page, change the following settings:
50
50
@@ -66,13 +66,13 @@ After the new sync group is created and deployed, **Add sync members (step 2)**
66
66
67
67
In the **Hub Database** section, enter existing credentials for the server on which the hub database is located. Don't enter *new* credentials in this section.
In the **Member Database** section, optionally add an Azure SQL Database to the sync group by selecting **Add an Azure SQL Database**. The **Configure Azure SQL Database** page opens.
On the **Configure Azure SQL Database** page, change the following settings:
78
78
@@ -95,7 +95,7 @@ In the **Member Database** section, optionally add an on-premises SQL Server to
95
95
96
96
1. Select **Choose the Sync Agent Gateway**. The **Select Sync Agent** page opens.
97
97
98
-

98
+

99
99
100
100
1. On the **Choose the Sync Agent** page, choose whether to use an existing agent or create an agent.
101
101
@@ -116,32 +116,32 @@ In the **Member Database** section, optionally add an on-premises SQL Server to
116
116
117
117
1. On the SQL Server computer, locate and run the Client Sync Agent app.
118
118
119
-

119
+

120
120
121
121
1. In the sync agent app, select **Submit Agent Key**. The **Sync Metadata Database Configuration** dialog box opens.
122
122
123
123
1. In the **Sync Metadata Database Configuration** dialog box, paste in the agent key copied from the Azure portal. Also provide the existing credentials for the server on which the metadata database is located. (If you created a metadata database, this database is on the same server as the hub database.) Select **OK** and wait for the configuration to finish.
124
124
125
-

125
+

126
126
127
127
> [!NOTE]
128
128
> If you get a firewall error, create a firewall rule on Azure to allow incoming traffic from the SQL Server computer. You can create the rule manually in the portal or in SQL Server Management Studio (SSMS). In SSMS, connect to the hub database on Azure by entering its name as <hub_database_name>.database.windows.net.
129
129
130
130
1. Select **Register** to register a SQL Server database with the agent. The **SQL Server Configuration** dialog box opens.
131
131
132
-

132
+

133
133
134
134
1. In the **SQL Server Configuration** dialog box, choose to connect using SQL Server authentication or Windows authentication. If you choose SQL Server authentication, enter the existing credentials. Provide the SQL Server name and the name of the database that you want to sync and select **Test connection** to test your settings. Then select **Save** and the registered database appears in the list.
135
135
136
-

136
+

137
137
138
138
1. Close the Client Sync Agent app.
139
139
140
140
1. In the portal, on the **Configure On-Premises** page, select **Select the Database**.
141
141
142
142
1. On the **Select Database** page, in the **Sync Member Name** field, provide a name for the new sync member. This name is distinct from the name of the database itself. Select the database from the list. In the **Sync Directions** field, select **Bi-directional Sync**, **To the Hub**, or **From the Hub**.
143
143
144
-

144
+

145
145
146
146
1. Select **OK** to close the **Select Database** page. Then select **OK** to close the **Configure On-Premises** page and wait for the new sync member to be created and deployed. Finally, select **OK** to close the **Select sync members** page.
147
147
@@ -152,7 +152,7 @@ In the **Member Database** section, optionally add an on-premises SQL Server to
152
152
153
153
After the new sync group members are created and deployed, **Configure sync group (step 3)** is highlighted in the **New sync group** page.
1. On the **Tables** page, select a database from the list of sync group members and select **Refresh schema**.
158
158
@@ -162,7 +162,7 @@ After the new sync group members are created and deployed, **Configure sync grou
162
162
163
163
1. By default, databases are not synced until scheduled or manually run. To run a manual sync, navigate to your SQL database in the Azure portal, select **Sync to other databases**, and select the sync group. The **Data Sync** page opens. Select **Sync**.
Copy file name to clipboardExpand all lines: articles/azure-sql/database/features-comparison.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
@@ -132,7 +132,7 @@ The Azure platform provides a number of PaaS capabilities that are added as an a
132
132
| Scaling up or down (online) | Yes, you can either change DTU or reserved vCores or max storage with the minimal downtime. | Yes, you can change reserved vCores or max storage with the minimal downtime. |
133
133
|[SQL Alias](https://docs.microsoft.com/sql/database-engine/configure-windows/create-or-delete-a-server-alias-for-use-by-a-client)| No, use [DNS Alias](dns-alias-overview.md)| No, use [Clicongf](https://techcommunity.microsoft.com/t5/Azure-Database-Support-Blog/Lesson-Learned-33-How-to-make-quot-cliconfg-quot-to-work-with/ba-p/369022) to set up alias on the client machines. |
|[SQL Data Sync](data-sync-sql-server-configure.md)| Yes | No |
135
+
|[SQL Data Sync](sql-data-sync-sql-server-configure.md)| Yes | No |
136
136
|[SQL Server Analysis Services (SSAS)](https://docs.microsoft.com/sql/analysis-services/analysis-services)| No, [Azure Analysis Services](https://azure.microsoft.com/services/analysis-services/) is a separate Azure cloud service. | No, [Azure Analysis Services](https://azure.microsoft.com/services/analysis-services/) is a separate Azure cloud service. |
137
137
| [SQL Server Integration Services (SSIS)](https://docs.microsoft.com/sql/integration-services/sql-server-integration-services) | Yes, with a managed SSIS in Azure Data Factory (ADF) environment, where packages are stored in SSISDB hosted by Azure SQL Database and executed on Azure SSIS Integration Runtime (IR), see [Create Azure-SSIS IR in ADF](https://docs.microsoft.com/azure/data-factory/create-azure-ssis-integration-runtime). <br/><br/>To compare the SSIS features in SQL Database and SQL Managed Instance, see [Compare SQL Database to SQL Managed Instance](../../data-factory/create-azure-ssis-integration-runtime.md#comparison-of-a-azure-sql-database-elastic-pool-and-sql-managed-instance). | Yes, with a managed SSIS in Azure Data Factory (ADF) environment, where packages are stored in SSISDB hosted by SQL Managed Instance and executed on Azure SSIS Integration Runtime (IR), see [Create Azure-SSIS IR in ADF](https://docs.microsoft.com/azure/data-factory/create-azure-ssis-integration-runtime). <br/><br/>To compare the SSIS features in SQL Database and SQL Managed Instance, see [Compare SQL Database to SQL Managed Instance](../../data-factory/create-azure-ssis-integration-runtime.md#comparison-of-a-azure-sql-database-elastic-pool-and-sql-managed-instance). |
138
138
|[SQL Server Reporting Services (SSRS)](https://docs.microsoft.com/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports)| No - [see Power BI](https://docs.microsoft.com/power-bi/)| No - [see Power BI](https://docs.microsoft.com/power-bi/)|
0 commit comments