Skip to main content
Data synchronization processes overview
Search
Search Indirect Tax Support Help and Support.

This article applies to:

  • Product: ONESOURCE Determination,ONESOURCE Indirect Tax

SDI

Legacy full synchronization method for migrating large configuration data sets between environments.

About SDI

For full configuration data synchronization, DA uses SDI as the original legacy method. SDI supports large-scale migration between environments and processes a complete data file.

Use SDI

The SDI process is robust but can be slow due to its methodical, entity-by-entity approach.
  1. Trigger
    : A configuration import or export usually begins an SDI sync. The
    Sync All Configuration
     button can also begin the process in certain scenarios.
  2. File Generation
    : The Mothership server generates a full XML file containing all configuration entities.
  3. Validation & Insertion
    : The client environment processes this file for 1 entity at a time. For each entity, it performs several checks and database operations:
    1. It checks if the entity already exists using a unique
      Entity Key
       (a combination of fields like name and tenant ID).
    2. It resolves all relationships with other data (foreign keys).
    3. It inserts or updates the entity in the client's database.
  4. Completion
    : This process continues until every entity in the file has been processed.

Key characteristics and known issues

  • Slow Performance:
     Because it validates each entity individually, the SDI process is very time-consuming. A configuration with 7 million entities can take more than 8 hours to generate the SDI file. It can take more than 7 hours to sync.
  • Constraint Violation Errors:
     The process can fail if it encounters data conflicts. Reordering rules can create a duplicate priority. This can cause the process to fail. Resolving these issues often requires intervention manually.
  • Independent IDs:
     SDI is designed for migration and doesn’t preserve the internal database IDs from the source environment. It creates new IDs in the target environment. This makes migration possible but direct comparisons harder.
Configuration Options:
 Streaming is the primary scheduling process, and SDI acts as a fallback. Administrators can turn on dedicated
SDI Mode
 through a customer overlay by turning off the streaming schedule and creating a recurring SDI schedule.
Scheduling Options:
 The following are turned on using the Overlay.
  • Config and content can be synced on different schedules
  • Use the CRON format for flexible scheduling (hourly, every 2 hours, every 12 hours, daily)
note
DA will replace the current SDI process with Bulk Import.

Related Content