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
Change Tracking is a lightweight solution that provides an efficient data change tracking mechanism for applications, ETL processes, event capture, and auditing. This allows for quick and simple detection of changed data without the need for expensive and complex custom solutions traditionally involving a combination of triggers, timestamp columns, new tables to store tracking information, and cleanup processes.
21
+
Change Tracking is a lightweight solution that provides an efficient data change tracking mechanism for applications, ETL processes, event capture, and auditing. This allows for quick and basic detection of changed data without the need for expensive and complex custom solutions traditionally involving a combination of triggers, timestamp columns, new tables to store tracking information, and cleanup processes.
22
22
23
23
## Stored procedures
24
24
@@ -28,7 +28,7 @@ Change Tracking is a lightweight solution that provides an efficient data change
Removes data from the management data warehouse based on a retention policy. This procedure is executed daily by the mdw_purge_data [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Agent job against the management data warehouse associated with the specified instance. You can use this stored procedure to perform an on-demand removal of data from the management data warehouse.
26
+
Removes data from the management data warehouse based on a retention policy. This procedure is executed daily by the `mdw_purge_data`[!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Agent job against the management data warehouse associated with the specified instance. You can use this stored procedure to perform an on-demand removal of data from the management data warehouse.
The number of days to retain data in the management data warehouse tables. Data with a time stamp older than *@retention_days* is removed. *@retention_days* is **smallint**, with a default of `NULL`. If specified, the value must be positive. When NULL, the value in the valid_through column in the `core.snapshots` view determines the rows that are eligible for removal.
45
+
The number of days to retain data in the management data warehouse tables. Data with a time stamp older than *@retention_days* is removed. *@retention_days* is **smallint**, with a default of `NULL`. If specified, the value must be positive. When `NULL`, the value in the valid_through column in the `core.snapshots` view determines the rows that are eligible for removal.
46
46
47
47
#### [ @instance_name = ] '*instance_name*'
48
48
49
49
The name of the instance for the collection set. *@instance_name* is **sysname**, with a default of `NULL`.
50
50
51
-
*instance_name* must be the fully qualified instance name, which consists of the computer name and the instance name in the form *computername*\\*instancename*. When NULL, the default instance on the local server is used.
51
+
*instance_name* must be the fully qualified instance name, which consists of the computer name and the instance name in the form `<computername>\<instancename>`. When `NULL`, the default instance on the local server is used.
The GUID for the collection set. *@collection_set_uid* is **uniqueidentifier**, with a default of `NULL`. When NULL, qualifying rows from all collection sets are removed. To obtain this value, query the `syscollector_collection_sets` catalog view.
55
+
The GUID for the collection set. *@collection_set_uid* is **uniqueidentifier**, with a default of `NULL`. When `NULL`, qualifying rows from all collection sets are removed. To obtain this value, query the `syscollector_collection_sets` catalog view.
56
56
57
57
#### [@duration = ]*duration*
58
58
59
-
The maximum number of minutes the purge operation should run. *@duration* is **smallint**, with a default of `NULL`. If specified, the value must be zero or a positive integer. When NULL, the operation runs until all qualified rows are removed or the operation is manually stopped.
59
+
The maximum number of minutes the purge operation should run. *@duration* is **smallint**, with a default of `NULL`. If specified, the value must be zero or a positive integer. When `NULL`, the operation runs until all qualified rows are removed or the operation is manually stopped.
60
60
61
61
## Return code values
62
62
@@ -78,7 +78,7 @@ Requires membership in the **mdw_admin** (with EXECUTE permission) fixed databas
78
78
79
79
### A. Run sp_purge_data with no parameters
80
80
81
-
The following example executes `core.sp_purge_data` without specifying any parameters. Therefore, the default value of NULL is used for all parameters, with the associated behavior.
81
+
The following example executes `core.sp_purge_data` without specifying any parameters. Therefore, the default value of `NULL` is used for all parameters, with the associated behavior.
82
82
83
83
```sql
84
84
USE <management_data_warehouse>;
@@ -98,7 +98,7 @@ GO
98
98
99
99
### C. Specify an instance name and collection set
100
100
101
-
The following example removes data from the management data warehouse for a given collection set on the specified instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Because @retention_days is not specified, the value in the valid_through column in the `core.snapshots` view is used to determine the rows for the collection set that are eligible for removal.
101
+
The following example removes data from the management data warehouse for a given collection set on the specified instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. Because *@retention_days* isn't specified, the value in the `valid_through` column in the `core.snapshots` view is used to determine the rows for the collection set that are eligible for removal.
SQL Server supports the following system stored procedures that are used to work with the data collector and the following components: collection sets, collection items, and collection types.
23
23
24
24
> [!IMPORTANT]
25
-
> Unlike regular stored procedures, the parameters for data collector stored procedures are strictly typed and do not support automatic data type conversion. If these parameters are not called with the correct input parameter data types, as specified in the argument description, the stored procedure returns an error.
25
+
> Unlike regular stored procedures, the parameters for data collector stored procedures are strictly typed and don't support automatic data type conversion. If these parameters aren't called with the correct input parameter data types, as specified in the argument description, the stored procedure returns an error.
26
26
27
27
:::row:::
28
28
:::column:::
@@ -71,16 +71,16 @@ SQL Server supports the following system stored procedures that are used to work
71
71
72
72
The following stored procedures are for internal use only:
Copy file name to clipboardExpand all lines: docs/relational-databases/system-stored-procedures/database-maintenance-plan-stored-procedures-transact-sql.md
[!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] supports the following system stored procedures that are used to set up maintenance tasks. These stored procedures are used with database maintenance plans. This feature has been replaced with maintenance plans which do not use these stored procedures. Use these procedures to maintain database maintenance plans on installations that were upgraded from a previous version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)].
22
+
[!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] supports the following system stored procedures that are used to set up maintenance tasks. These stored procedures are used with database maintenance plans. This feature has been replaced with maintenance plans which don't use these stored procedures. Use these procedures to maintain database maintenance plans on installations that were upgraded from a previous version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)].
0 commit comments