Close popover

Table of Contents

Migrating data between Decision Data Store data sets

Version:

You can migrate data between two sibling Decision Data Store data sets. By using this option, you can transfer records between sibling data sets that are part of different rulesets or sibling data sets that part of different versions of the same ruleset and do not share a data schema (for example, as a result of having a different set of exposed properties). With this option, you can quickly and efficiently migrate data between related rulesets and re-use it in different applications. Additionally, no data is lost when you migrate data between data sets that have different schemes.

  1. Access the Data Set rule that you want to migrate by performing the following actions:

    1. In Dev Studio, click Records Data Model Data Set ,

    2. Click the data set name. This data set must be of type Decision Data Store.

  2. On the Decision data store tab, in the Data migration section, click Migrate data.

    This section is visible only if the current data set has a sibling rule in another version of the same ruleset or is part of a different ruleset but has the same name and Applies To class.
  3. Expand the Source data set version list and select the data set from which you want to migrate data to the current data set.

  4. Optional:

    Truncate the data in the source or destination data set by selecting an available option in the Migration options section:

    • Truncate the source data set after migration – Removes the data from the source data set after the migration process finishes. Use this option when you do not need the data in the source data set because, for example, that data set is part of an obsolete application ruleset.
    • Truncate the destination set before migration – Removes data from the current data set before the migration process starts and then moves the data from the source data set to the current data set. Select this option when you want to overwrite the data in the current data set with the data from the source data set. If this option is not selected, the migration process will overwrite any data with the same keys and append or insert new records in the destination data set. You can select this option if, for example, the previous migration process was unsuccessful and only a portion of the data was saved.
  5. Click Migrate.

    The migration process starts and a data flow run is triggered in the background that transfers the data over from the source to the destination and performs truncating, if selected. You can view migration process by clicking Open data flow run.

  • Types of Data Set rules

    Learn about the types of data set rules that you can create in Pega Platform.

  • Configuring a data flow to update a single property only

    You can update a single property as a result of a data flow run. By using the Cassandra architecture in Decision Data Store you can update or append values for individual properties, instead of updating the full data record each time that a single property value changes. This solution can improve system performance by decreasing the system resources that are required to update your data records.

  • About Data Set rules

    Data sets define collections of records, allowing you to set up instances that make use of data abstraction to represent data stored in different sources and formats. Depending on the type selected when creating a new instance, data sets represent Visual Business Director (VBD) data sources, data in database tables or data in decision data stores. Through the data management operations for each data set type, you can read, insert and remove records. Data sets are used on their own through data management operations, as part of combined data

  • Data Set rules - Completing the Create, Save As, or Specialization form

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.