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/sql-data-sync-data-sql-server-sql-database.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This overview introduces SQL Data Sync for Azure, which allows you
4
4
author: WilliamDAssafMSFT
5
5
ms.author: wiassaf
6
6
ms.reviewer: mathoma, hudequei
7
-
ms.date: 04/04/2025
7
+
ms.date: 11/03/2025
8
8
ms.service: azure-sql-database
9
9
ms.subservice: sql-data-sync
10
10
ms.topic: concept-article
@@ -164,6 +164,7 @@ Provisioning and deprovisioning during sync group creation, update, and deletion
164
164
- An Azure Elastic jobs database can't be used as the SQL Data Sync Metadata database, and vice versa.
165
165
- SQL Data Sync isn't supported for [ledger databases](/sql/relational-databases/security/ledger/ledger-database-ledger).
166
166
- Data Sync is not a disaster recovery or high availability tool and does not synchronize its own Sync Group information. There is no automatic disaster recovery for Data Sync.
167
+
- Data Sync does not support [Network security perimeter (NSP)](/azure/private-link/network-security-perimeter-concepts).
Copy file name to clipboardExpand all lines: docs/includes/ssrs-no-pin-2-power-bi.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
@@ -10,4 +10,4 @@ ms.custom: include file
10
10
---
11
11
12
12
>[!NOTE]
13
-
>Pinning paginated reports to Power BI dashboards is deprecated for all releases of SQL Server Reporting Services after SQL Server Reporting Services 2019. It is discontinued starting in SQL Server Reporting Services 2022 and Power BI Report Server.
13
+
>Pinning paginated reports to Power BI dashboards is deprecated and discontinued for all releases of SQL Server Reporting Services and Power BI Report Server.
Use the **Maintenance Plan (Design Tab)**to specify the properties of a maintenance plan and its subplans. Drag tasks from the Toolbox to the plan designer. Right-click groups of tasks to create branching execution paths. Maintenance plans are saved as [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] packages that are run by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent jobs.
21
+
Use the maintenance plan designer to specify the properties of a maintenance plan and its subplans. Drag tasks from the **Toolbox** to the plan designer. Right-click groups of tasks to create branching execution paths. Maintenance plans are saved as [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] packages that are run by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent jobs.
22
22
23
23
## Options
24
24
25
-
-**Add Subplan**
25
+
#### Add Subplan
26
26
27
-
Add a subplan that you can configure.
27
+
Add a subplan that you can configure.
28
28
29
-
-**Subplan Properties**
29
+
#### Subplan Properties
30
30
31
-
Display the **Subplan Properties** dialog box. Select a subplan in the grid and select this icon to enter a name, description, and schedule for the subplan. You can also double-click the subplan in the grid to display the **Subplan Properties** dialog box. Subplan names are limited to 128 characters and subplan descriptions are limited to 512 characters.
31
+
Display the **Subplan Properties** dialog box. Select a subplan in the grid and select this icon to enter a name, description, and schedule for the subplan. You can also double-click the subplan in the grid to display the **Subplan Properties** dialog box. Subplan names are limited to 128 characters and subplan descriptions are limited to 512 characters.
32
32
33
-
-**Delete Selected Subplan**
33
+
#### Delete Selected Subplan
34
34
35
-
Delete the selected subplan.
35
+
Delete the selected subplan.
36
36
37
-
-**Subplan Schedule**
37
+
#### Subplan Schedule
38
38
39
-
Display the **Job Schedule Properties** dialog box. Select a subplan in the grid and select this icon to configure a schedule for the subplan.
39
+
Display the **Job Schedule Properties** dialog box. Select a subplan in the grid and select this icon to configure a schedule for the subplan.
40
40
41
-
-**Remove Schedule**
41
+
#### Remove Schedule
42
42
43
-
Remove a schedule from the selected subplan.
43
+
Remove a schedule from the selected subplan.
44
44
45
-
-**Manage Connections**
45
+
#### Manage Connections
46
46
47
-
Display the **Manage Connections** dialog box. Used to add additional[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance connections to the maintenance plan. Each maintenance task in the subplan editor can use any of these connections. When executing, the maintenance plan makes a connection from the maintenance plan server to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] servers specified, using the connection credentials.
47
+
Display the **Manage Connections** dialog box. Used to add extra[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance connections to the maintenance plan. Each maintenance task in the subplan editor can use any of these connections. When the maintenance plan executes, it makes a connection from the maintenance plan server to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] servers specified, using the connection credentials.
48
48
49
-
-**Reporting and Logging**
49
+
#### Reporting and Logging
50
50
51
-
Display the **Reporting and Logging** dialog box, used to manage reports concerning maintenance plan activity, and to configure logging to the local or a remote server.
51
+
Display the **Reporting and Logging** dialog box, used to manage reports concerning maintenance plan activity, and to configure logging to the local or a remote server.
52
52
53
-
-**Servers**
53
+
#### Servers
54
54
55
-
Display the **Servers** dialog box, which is used to select the servers where the subplan tasks will be run. This option is enabled only on master servers in multiserver environments. For more information, see [Create a Multiserver Environment](../../ssms/agent/create-a-multiserver-environment.md).
55
+
Display the **Servers** dialog box, which is used to select the servers where the subplan tasks will run. This option is enabled only on master servers in multiserver environments. For more information, see [Create a Multiserver Environment](../../ssms/agent/create-a-multiserver-environment.md).
56
56
57
-
-**Name**
57
+
#### Name
58
58
59
-
Display the maintenance plan name. For new maintenance plans, the name is specified in a dialog box before the maintenance plan designer opens. To rename a maintenance plan, right-click the plan in Object Explorer, and then select **Rename**.
59
+
Display the maintenance plan name. For new maintenance plans, the name is specified in a dialog box before the maintenance plan designer opens. To rename a maintenance plan, right-click the plan in Object Explorer, and then select **Rename**.
60
60
61
-
-**Description**
61
+
#### Description
62
62
63
-
View or specify a description for the maintenance plan. The maximum length for a description is 512 characters.
63
+
View or specify a description for the maintenance plan. The maximum length for a description is 512 characters.
64
64
65
-
-**Designer Surface**
65
+
#### Designer Surface
66
66
67
-
Design and maintain maintenance plans. Use the designer surface to add maintenance tasks to a plan, remove tasks from a plan, specify precedence links between the tasks, and indicate task branching and parallelism.
67
+
Design and maintain maintenance plans. The following section describes the design surface in more detail.
68
68
69
-
A precedence link between two tasks establishes a relationship between the tasks. The second task (the *dependent task*) executes only if the execution result of the first task (the *precedent task*) matches specified criteria. Typically the execution result specified is **Success**, **Failure**, or **Completion**. The maintenance plan designer surface is based on the [!INCLUDE[ssIS](../../includes/ssis-md.md)] designer surface. For more information, see [Precedence Constraints](../../integration-services/control-flow/precedence-constraints.md).
69
+
## Use the design surface
70
70
71
-
As an example, a Defragment Index Task could be specified to execute only if a previous Check Database Integrity task completed successfully. The task precedence linkage feature also allows for error or failure conditions to be handled in a plan. For example, if the Check Database Integrity task failed, a Notify Operator task could notify a user or operator about the failure.
71
+
Use the designer surface to add maintenance tasks to a plan, remove tasks from a plan, specify precedence links between the tasks, and indicate task branching and parallelism.
72
72
73
-
Specifying tasks to execute after the failure of a predecessor task is an example of *task branching*.
73
+
### Add and remove tasks
74
+
75
+
To add a maintenance task to a plan, drag the task's icon from the **Maintenance Plan Tasks** toolbox to the plan design surface, or double-click the task in the toolbox, which adds that task to the currently active designer surface. If the **Maintenance Plan Tasks** toolbox isn't visible, choose **Toolbox** from the [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)]**View** menu. Expand the **Maintenance Plan Tasks** node in the **Toolbox** pane.
74
76
75
-
Indicating that two or more tasks begin simultaneously, for example upon the successful completion of a predecessor task, is an example of specifying *task parallelism*. All tasks with no constraints will start and run in parallel. Use constraints to delay tasks so earlier tasks complete first.
77
+
To remove a task from a plan, select the task in the designer surface and press the <kbd>Del</kbd> key, or right-click the task and then select **Delete**.
76
78
77
-
After a maintenance task is placed on the design surface, its properties can be edited as needed. For example, the specific database to back up in a Back Up Database Task is specified after the task is added the plan. Tasks on the design surface that aren't properly configured contain a red icon with a white x.
79
+
### Precedence links
78
80
79
-
To add a maintenance task to a plan, drag the task's icon from the **Maintenance Plan Tasks** toolbox to the plan design surface, or double-click the task in the toolbox, which adds that task to the currently active designer surface. If the **Maintenance Plan Tasks** toolbox isn't visible, choose**Toolbox** from the [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]**View** menu. Expand the **Maintenance Plan Tasks** node in the **Toolbox** pane.
81
+
A precedence link between two tasks establishes a relationship between the tasks. The second task (the *dependent task*) executes only if the execution result of the first task (the *precedent task*) matches specified criteria. Typically the execution result specified is **Success**, **Failure**, or**Completion**. The maintenance plan designer surface is based on the [!INCLUDE[ssIS](../../includes/ssis-md.md)]designer surface. For more information, see [Precedence Constraints](../../integration-services/control-flow/precedence-constraints.md).
80
82
81
-
To remove a task from a plan, select the task in the designer surface and press the **DELETE** key, or right-click the task and then select **Delete**.
83
+
As an example, a Defragment Index task could be specified to execute only if a previous Check Database Integrity task completed successfully. The task precedence linkage feature also allows for error or failure conditions to be handled in a plan. For example, if the Check Database Integrity task failed, a Notify Operator task could notify a user or operator about the failure.
82
84
83
85
To specify precedence links between two tasks, first drag the tasks to the design surface, and then select the task that occurs first (the precedent task), and drag the arrow to the dependent task. When a precedence link has been established, the designer displays an arrow linking the two tasks, with the precedent task pointing to the dependent task. By default, when a link is first established, the link's constraint is set such that the dependent task only executes if the execution result of the precedent task is **Success**.
84
86
85
-
To change the properties of a precedence link, double-click the link to launch the **Precedence Constraint Editor**. This provides many options for specifying the logical conditions that determine whether the dependent task executes. For example, the **Execution result** can be set to **Failure**, in which case the dependent task only executes if the precedent task fails. Modifying the execution result property of a link to **Success**, **Failure**, or **Completion**, can also be accomplished by right-clicking the link and then selecting from the context menu.
87
+
To change the properties of a precedence link, double-click the link to launch the **Precedence Constraint Editor**. This provides many options for specifying the logical conditions that determine whether the dependent task executes. For example, the **Execution result** can be set to **Failure**, in which case the dependent task only executes if the precedent task fails. You can modify the execution result property of a link to **Success**, **Failure**, or **Completion**, by right-clicking the link and then selecting from the context menu.
88
+
89
+
### Task branching and task parallelism
90
+
91
+
Specifying tasks to execute after the failure of a predecessor task is an example of *task branching*.
92
+
93
+
Indicating that two or more tasks begin simultaneously, for example upon the successful completion of a predecessor task, is an example of specifying *task parallelism*. All tasks with no constraints start and run in parallel. Use constraints to delay tasks so earlier tasks complete first.
86
94
87
95
To specify task branching, first create precedence links between two tasks. Then, put another dependent task on the design surface that executes on a different outcome than the first dependent task. Select the predecessor task, and drag the second arrow from the precedent task to the dependent task. To change the execution result (**Success**, **Failure**, **Completion**) that causes a dependent task to execute, double-click the link arrow and modify the **Execution result** field. Alternatively, right-click the link and select the desired execution result value from the shortcut menu.
88
96
89
97
To specify task parallelism, link two or more dependent tasks to a single precedent task. Modify the properties of the precedence links so that the links pointing to the dependent tasks that run in parallel have the same value for their execution result fields.
90
98
91
-
## Additional features available from the shortcut menu
99
+
### Edit task properties
100
+
101
+
After a maintenance task is placed on the design surface, its properties can be edited as needed. For example, the specific database to back up in a Back Up Database task is specified after the task is added to the plan. Tasks on the design surface that aren't properly configured contain a red icon with a white x.
102
+
103
+
## Extra features available from the shortcut menu
92
104
93
-
To see additional options, select one or more tasks on the design surface, and then right-click, to open the shortcut menu. In addition to typical **Cut**, **Copy**, **Paste**, **Delete**, and **Select All**, the following special options are available for some tasks.
105
+
To see more options, select one or more tasks on the design surface, and then right-click, to open the shortcut menu. In addition to typical **Cut**, **Copy**, **Paste**, **Delete**, and **Select All**, the following special options are available for some tasks.
94
106
95
-
-**Add Annotation**
107
+
#### Add Annotation
96
108
97
-
Adds a descriptive note to the design surface.
109
+
Adds a descriptive note to the design surface.
98
110
99
-
-**Edit**
111
+
#### Edit
100
112
101
-
Opens the property dialog box for the task.
113
+
Opens the property dialog box for the task.
102
114
103
-
-**Disable**
115
+
#### Disable
104
116
105
-
Makes the task temporarily unavailable.
117
+
Makes the task temporarily unavailable.
106
118
107
-
-**Enable**
119
+
#### Enable
108
120
109
-
Restores a disabled task.
121
+
Restores a disabled task.
110
122
111
-
-**Group**
123
+
#### Group
112
124
113
-
Creates a group that contains one or more tasks.
125
+
Creates a group that contains one or more tasks.
114
126
115
-
-**Ungroup**
127
+
#### Ungroup
116
128
117
-
Removes tasks from a group.
129
+
Removes tasks from a group.
118
130
119
-
-**Autosize**
131
+
#### Autosize
120
132
121
-
Sets the size of each task to the optimal size for that task.
133
+
Sets the size of each task to the optimal size for that task.
122
134
123
-
-**Collapse**
135
+
#### Collapse
124
136
125
-
Hides tasks within a group.
137
+
Hides tasks within a group.
126
138
127
-
-**Expand**
139
+
#### Expand
128
140
129
-
Shows the tasks in a group that were previously hidden using **Collapse**.
141
+
Shows the tasks in a group that were previously hidden using **Collapse**.
130
142
131
-
-**Zoom**
143
+
#### Zoom
132
144
133
-
Changes the size of the tasks on the design surface
145
+
Changes the size of the tasks on the design surface
134
146
135
-
## See also
147
+
## Related content
136
148
137
-
-[Maintenance Plans](maintenance-plans.md)
138
-
-[Create a Maintenance Plan](create-a-maintenance-plan.md)
149
+
-[Maintenance plans](maintenance-plans.md)
150
+
-[Create a maintenance plan](create-a-maintenance-plan.md)
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments