Merge pull request #18391 from MicrosoftDocs/master

1/28 PM Publish

Author: huypub

docs/integration-services/control-flow/cdc-control-task-custom-properties.md

@@ -21,7 +21,7 @@ ms.author: chugu
 
 |Property name|Data Type|Description|  
 |-------------------|---------------|-----------------|  
-|Connection|ADO.NET Connection|An ADO.NET connection to the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC database for access to the change tables and to the CDC State if stored in the same database.<br /><br /> The connection must be to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database that is enabled for CDC and where the selected change table is located.|  
+|Connection|ADO.NET Connection|An ADO.NET connection to the [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC database for access to the change tables and to the CDC State if stored in the same database.<br /><br /> The connection must be to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database that is enabled for CDC and where the selected change table is located.|  
 |TaskOperation|Integer (enumeration)|The selected operation for the CDC control task. The possible values are **Mark Initial Load Start**, **Mark Initial Load End**, **Mark CDC Start**, **Get Processing Range**, **Mark Processed Range**, and **Reset CDC State**.<br /><br /> If you select **MarkCdcStart**, **MarkInitialLoadStart**, or **MarkInitialLoadEnd** when working on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  **db_owner** or **sysadmin**.<br /><br /> For more information about these operations, see [CDC Control Task Editor](./cdc-control-task.md) and [CDC Control Task](../../integration-services/control-flow/cdc-control-task.md).|  
 |OperationParameter|String|Currently used with the **MarkCdcStart** operation. This parameter allows additional input required for the specific operation. For example, the LSN number required for the **MarkCdcStart** operation|  
 |StateVariable|String|An SSIS package variable that stores the CDC state of the current CDC context. The CDC Control task reads and writes the state to the **StateVariable** and does not load it or store it to a persistent storage unless **AutomaticStatePersistence** is selected. See [Define a State Variable](../../integration-services/data-flow/define-a-state-variable.md).|  

docs/integration-services/control-flow/cdc-control-task.md

@@ -31,9 +31,9 @@ ms.author: chugu
 |Operation|Description|  
 |---------------|-----------------|  
 |ResetCdcState|This operation is used to reset the persistent CDC state associated with the current CDC context. After this operation is run, the current maximum LSN from the LSN-timestamp `sys.fn_cdc_get_max_lsn` table becomes the start of the range for the next processing range. This operation requires a connection to the source database.|  
-|MarkInitialLoadStart|This operation is used at the beginning of an initial-load package to record the current LSN in the source database before the initial-load package starts reading the source tables. This requires a connection to the source database to call `sys.fn_cdc_get_max_lsn`.<br /><br /> If you select MarkInitialLoadStart when working on [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  db_owner or sysadmin.|  
-|MarkInitialLoadEnd|This operation is used at the end of an initial-load package to record the current LSN in the source database after the initial-load package finished reading the source tables. This LSN is determined by recording the current time when this operation occurred and then querying the `cdc.lsn_time_`mapping table in the CDC database looking for a change that occurred after that time.<br /><br /> If you select MarkInitialLoadEnd when working on [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC (that is , not Oracle) the user specified in the connection manager must be either  db_owner or sysadmin.|  
-|MarkCdcStart|This operation is used when then the initial load is made from a snapshot database. In this case, the change processing should start immediately after the snapshot LSN. You can specify the name of the snapshot database to use and the CDC Control task queries [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] for the snapshot LSN. You also have the option to directly specify the snapshot LSN.<br /><br /> If you select MarkCdcStart when working on [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC (that is , not Oracle) the user specified in the connection manager must be either  db_owner or sysadmin.|  
+|MarkInitialLoadStart|This operation is used at the beginning of an initial-load package to record the current LSN in the source database before the initial-load package starts reading the source tables. This requires a connection to the source database to call `sys.fn_cdc_get_max_lsn`.<br /><br /> If you select MarkInitialLoadStart when working on [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  db_owner or sysadmin.|  
+|MarkInitialLoadEnd|This operation is used at the end of an initial-load package to record the current LSN in the source database after the initial-load package finished reading the source tables. This LSN is determined by recording the current time when this operation occurred and then querying the `cdc.lsn_time_`mapping table in the CDC database looking for a change that occurred after that time.<br /><br /> If you select MarkInitialLoadEnd when working on [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC (that is , not Oracle) the user specified in the connection manager must be either  db_owner or sysadmin.|  
+|MarkCdcStart|This operation is used when then the initial load is made from a snapshot database. In this case, the change processing should start immediately after the snapshot LSN. You can specify the name of the snapshot database to use and the CDC Control task queries [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] for the snapshot LSN. You also have the option to directly specify the snapshot LSN.<br /><br /> If you select MarkCdcStart when working on [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC (that is , not Oracle) the user specified in the connection manager must be either  db_owner or sysadmin.|  
 
  The following operations are used to manage the processing range:  
 
@@ -102,17 +102,17 @@ ms.author: chugu
 
 -   **Mark initial load start**: This operation is used when executing an initial load from an active database without a snapshot. It is invoked at the beginning of an initial-load package to record the current LSN in the source database before the initial-load package starts reading the source tables. This requires a connection to the source database.  
 
-     If you select **Mark Initial Load Start** when working on [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  **db_owner** or **sysadmin**.  
+     If you select **Mark Initial Load Start** when working on [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  **db_owner** or **sysadmin**.  
 
 -   **Mark initial load end**: This operation is used when executing an initial load from an active database without a snapshot. It is invoked at the end of an initial-load package to record the current LSN in the source database after the initial-load package finished reading the source tables. This LSN is determined by recording nthe current time when this operation occurred and then querying the `cdc.lsn_time_`mapping table in the CDC database looking for a change that occurred after that time  
 
-     If you select **Mark Initial Load End** when working on [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  **db_owner** or **sysadmin**.  
+     If you select **Mark Initial Load End** when working on [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  **db_owner** or **sysadmin**.  
 
 -   **Mark CDC start**: This operation is used when then the initial load is made from a snapshot database or from a quiescence database. It is invoked at any point within the initial load package. The operation accepts a parameter that can be a snapshot LSN, a name of a snapshot database (from which the snapshot LSN will be derived automatically) or it can be left empty, in which case the current database LSN is used as the start LSN for the change processing package.  
 
      This operation is used instead of the Mark Initial Load Start/End operations.  
 
-     If you select **Mark CDC Start** when working on [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  **db_owner** or **sysadmin**.  
+     If you select **Mark CDC Start** when working on [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC (that is, not Oracle) the user specified in the connection manager must be either  **db_owner** or **sysadmin**.  
 
 -   **Get processing range**: This operation is used in a change processing package before invoking the data flow that uses the CDC Source data flow. It establishes a range of LSNs that the CDC Source data flow reads when invoked. The range is stored in an SSIS package variable that is used by the CDC Source during data-flow processing.  
 

docs/integration-services/data-flow/cdc-flow-components.md

@@ -19,9 +19,9 @@ ms.author: chugu
 
   The Change Data Capture Components by Attunity for Microsoft [!INCLUDE[ssISCurrent](../../includes/ssiscurrent-md.md)] help SSIS developers work with CDC and reduce the complexity of CDC packages.  
 
- The SSIS CDC components are designed to work with the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC feature where the source tables are either the same [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] database or an Oracle database (when using the Oracle CDC Service for [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]). Partitioned tables are supported.  
+ The SSIS CDC components are designed to work with the [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC feature where the source tables are either the same [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] database or an Oracle database (when using the Oracle CDC Service for [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)]). Partitioned tables are supported.  
 
- The components include Control and Data Flow components that streamline the experience of reading and processing change data in SSIS packages. The components can be added to the component library in Microsoft [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)], but are installed separately.  
+ The components include Control and Data Flow components that streamline the experience of reading and processing change data in SSIS packages. The components can be added to the component library in Microsoft [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)], but are installed separately.  
 
  The following are the Change Data Capture Components by Attunity:  
 
@@ -56,29 +56,29 @@ The CDC components for SSIS are supported on the following operating systems and
 -   Windows Server 2016
 
 ### Running the Installation Program  
- Before you run the installation wizard, be sure that the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)][!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] is closed. Then follow the directions in the installation wizard.  
+ Before you run the installation wizard, be sure that the [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)][!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] is closed. Then follow the directions in the installation wizard.  
 
 ### Restart SSIS Service 
 After you install the CDC components, you must restart the SSIS service to be sure that the components work correctly when developing packages in the SQL [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)].  
 
 A message is displayed after you install the components. Click **Yes** when prompted.  
 
 ### Uninstalling the Microsoft CDC Components  
- You uninstall the CDC source, CDC splitter, or CDC Control task, by using the uninstall wizard. If you are using the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)][!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] for package development, make sure the [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] is closed before running the uninstall wizard.  
+ You uninstall the CDC source, CDC splitter, or CDC Control task, by using the uninstall wizard. If you are using the [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)][!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] for package development, make sure the [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] is closed before running the uninstall wizard.  
 
 ## Benefits  
- The CDC Components for [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)][!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] components allow SSIS developers to easily build SSIS packages that process change data. These components enhance the ability of SSIS developers to deal with CDC and reduce the complexity of CDC packages.  
+ The CDC Components for [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)][!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] components allow SSIS developers to easily build SSIS packages that process change data. These components enhance the ability of SSIS developers to deal with CDC and reduce the complexity of CDC packages.  
 
  The SSIS CDC components are used to provide the change data in a way that is easy to further process it for replication, loading a data warehouse, updating slowly changing dimensions for OLAP, auditing changes, or for additional possible uses. The type of further processing used is determined by the SSIS developer.  
 
- The SSIS CDC components are designed to work with the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC feature with change tables that are in the same [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] database.  
+ The SSIS CDC components are designed to work with the [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC feature with change tables that are in the same [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] database.  
 
 ## Getting Started with the Change Data Capture Components  
  A typical CDC package processes changes to a group of tables. The basic control flow part of this type of CDC package is shown in the following figure. This package is called a trickle-feed processing package.  
 
  ![Trickle Feed Processing Package Control Flow](../../integration-services/data-flow/media/tricklefeedprocessing.gif "Trickle Feed Processing Package Control Flow")  
 
- This [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)][!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] Control Flow contains two CDC Control Tasks and the Data Flow task. The first task called **Get CDC Processing Range** establishes the LSN range for the changes that are processed in the data-flow task called **Process Changes**. This range is established based on what was processed during the last package run and was saved in a persistent store.  
+ This [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)][!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] Control Flow contains two CDC Control Tasks and the Data Flow task. The first task called **Get CDC Processing Range** establishes the LSN range for the changes that are processed in the data-flow task called **Process Changes**. This range is established based on what was processed during the last package run and was saved in a persistent store.  
 
  For more information about using the CDC Control Task, see [CDC Control Task](../../integration-services/control-flow/cdc-control-task.md) and [CDC Control Task Editor](../control-flow/cdc-control-task.md).  
 
@@ -136,13 +136,13 @@ A message is displayed after you install the components. Click **Yes** when prom
  This section lists some security considerations related to the use of the CDC components in SSIS.  
 
 ### Access Authorization to Change Data  
- Trickle-feed update packages need access to [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC functions. Such access is granted, by default, to members of the **db_owner** fixed database role. Because the **db_owner** is a powerful role, when defining capture instances within [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] it is recommended to associate a gating security role to each capture instance that allows the SSIS CDC package to use a much more restricted user for processing the changes.  
+ Trickle-feed update packages need access to [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC functions. Such access is granted, by default, to members of the **db_owner** fixed database role. Because the **db_owner** is a powerful role, when defining capture instances within [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] it is recommended to associate a gating security role to each capture instance that allows the SSIS CDC package to use a much more restricted user for processing the changes.  
 
 ### Access to CDC Database Current LSN  
- The CDC Control task operations for marking the start LSN for change processing must be able to find the CDC Database current LSN. The components find the LSN by using the procedure **sp_replincrementlsn** from the master database. Execute permission on this procedure must be given to the login used for connecting to the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC database.  
+ The CDC Control task operations for marking the start LSN for change processing must be able to find the CDC Database current LSN. The components find the LSN by using the procedure **sp_replincrementlsn** from the master database. Execute permission on this procedure must be given to the login used for connecting to the [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC database.  
 
 ### Access to CDC States Table  
- The CDC States table is used for automatically persisting CDC States that need to be updatable by the login used for connecting to the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC database. As this table is created by the SSIS developer, set the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] system administrator as a user who is authorized to create [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] databases and perform administrative and maintenance tasks. In addition, a [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] system administrator who works with CDC enabled databases must be knowledgeable about [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC technology and implementation.  
+ The CDC States table is used for automatically persisting CDC States that need to be updatable by the login used for connecting to the [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC database. As this table is created by the SSIS developer, set the [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] system administrator as a user who is authorized to create [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] databases and perform administrative and maintenance tasks. In addition, a [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] system administrator who works with CDC enabled databases must be knowledgeable about [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] CDC technology and implementation.  
 
 ## Grouping Tables for CDC Processing  
  Database projects range in size from several tables to many thousands of tables. When designing initial load and CDC packages, it is beneficial to group tables in much smaller groups for easier management and efficiency. This section lists various considerations that impact the sorting of tables into small groups, where the tables in each are initially loaded and then updated as a group.