--- title: "Configure Workspace: Datastores" slug: "configure-workspace-datastores" updated: 2026-11-16T14:35:09Z published: 2026-11-16T14:35:09Z canonical: "skthelp.syniti.com/configure-workspace-datastores" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure Workspace: Datastores ## Overview After successfully creating a workspace, you are required to configure your workspace’s datastores details in the Datastores tab to setup your data replication project. Accessing the newly created workspace displays the Datastores tab which is the primary view of a workspace. The Datastores tab drives your project’s workspace. Datastores configuration involves setting up the following components to the newly created workspace: 1. [Target Datastores](/docs/configure-workspace-datastores#creating-target-datastores) 2. [Source Datastores](/docs/configure-workspace-datastores#creating-source-datastores) 3. [Replications](/docs/configure-workspace-datastores#creating-replications) ## Prerequisites - You must have the Replicate Developer or Replicate Administrator role assigned. - Ensure that you have created the Source and Target systems with its datastore connection details in the Catalog module. - Ensure that the connection’s Usage for the required Source and Target datastores is set to **Replication**. ## Creating Target Datastores A target datastore is a datasource where the snapshot of the source data or tables gets created, generally in a working database server or directly in your target system. Examples of target datastores can include, but are not limited to: - Snapshot datastores with the SRCxxx or TGTxxx prefixes - Working datastores with the WRKxxx prefix - External datastores like target systems or staging areas - Syniti Drives for file exports or reporting > [!NOTE] > Note > > A datastore can be registered as a target datastore only once across all workspaces. To add a target datastore: 1. In the Targets panel, click the **Add Target** button. The Add Target Datastore dialog box is displayed. 2. From the Type list, select the required datastore type. **SKP Catalog System** 1. From the Datastore list, select the target datastore configured in the Catalog module. > [!NOTE] > Note > > Only datastore connections with Usage set to Replication will be displayed on the Datastore list. > [!NOTE] > Note > > The Default Database and Default Schema values for the target datastores are fetched from the datastore configuration. If the datastore configuration does not include database and schema values, you can manually enter the Default Database and Default Schema values for this target datastore. 2. If you want to specify higher preference for this target datastore over others, enter a priority value in the Priority field. > [!NOTE] > Note > > The target datastores will be ordered using the Priority value. By default, this value for each target datastore is set at 1000, which provides equal preferences for all target datastore in a workspace, but ordered using the creation time of the target datastore. 3. Click **Save**. **Syniti Drive** > [!NOTE] > Note > > You can use [Syniti Drive](/v1/docs/syniti-drive) as the target datastore for file exports or reporting purposes. 1. From the Drives list, select the required drive. If the required drive is not listed, contact your Administrator to create one. 2. If you want to specify higher preference for this target datastore over others, enter a priority value in the Priority field. > [!NOTE] > Note > > The target datastores will be ordered using the Priority value. By default, this value for each target datastore is set at 1000, which provides equal preferences for all target datastore in a workspace, but ordered using the creation time of the target datastore. 3. Click **Save**. For creating file export replications, refer to [Adding File Replications](/v1/docs/configure-workspace-datastores#adding-file-replications) for more information. A target datastore is created successfully. If you need to create more target datastores, click the **Add Target** (**+**) button in the Targets panel. > [!NOTE] > Note > > Refer to [Working with the Targets Panel](/v1/docs/working-with-the-targets-panel) to learn more about the Targets panel and its usage. ## Creating Source Datastores A source datastore is a datasource where you need to take a data snapshot or copy the data from a source and move it to a target datastore. Examples of source datastores include, but are not limited to: - Legacy systems - Data from Syniti Construct - Data from working datastores - Snapshot tables of the target database for post-load reporting - Data from flat files To add a source datastore: 1. In the Sources panel, click the **Add Source** button. The Add Source Datastore dialog box is displayed. 2. From the Type list, select the required datastore type. **SKP Catalog System** > [!NOTE] > Note > > Ensure that the associated target datastore is displayed in this dialog box. 1. From the Datastore list, select the required source datastore configured in the Catalog module. The Default Database and Default Schema values for this source datastore are fetched from the datastore configuration. If values for these fields do not exist in the datastore configuration, then these fields will not be displayed in this dialog box. > [!NOTE] > Note > > Only datastore connections with Usage set to Replication will be displayed on the Datastore list. 2. If you want to specify higher preference for this source datastore over others, enter a priority value in the Priority field. > [!NOTE] > Note > > The source datastores will be ordered and executed using the Priority value. By default, this value for each source datastore is set at 1000, which provides equal preferences for all source datastores associated with a target datastore, but ordered using the creation time of the source datastore. 3. In the Client ID field, enter the required SAP Client value. SAP systems may contain multiple clients with different datasets and security configurations. > [!NOTE] > Note > > This value is used as a Source Filter in all replications for SAP ECC and SAP S/4HANA ODBC connections. 4. Click **Save**. **Syniti Drive** > [!NOTE] > Note > > Ensure that the associated target datastore is displayed in this dialog box. 1. From the Drives list, select the required drive. If the required drive is not listed, contact your Administrator to create one. 2. If you want to specify higher preference for this target datastore over others, enter a priority value in the Priority field. > [!NOTE] > Note > > The target datastores will be ordered using the Priority value. By default, this value for each target datastore is set at 1000, which provides equal preferences for all target datastore in a workspace, but ordered using the creation time of the target datastore. 3. Click **Save**. For creating file import replications, refer to [Adding File Replications](/v1/docs/configure-workspace-datastores#adding-file-replications) for more information. A source datastore is created successfully to the selected target datastore. If you need to create more source datastores, click the **Add Source** (**+**) icon in the Sources panel. > [!NOTE] > Note > > Refer to [Working with the Sources Panel](/v1/docs/working-with-the-sources-panel) to learn more about the Sources panel and its usage. ## Creating Replications You must now specify or add the required tables from the source datastore to replicate them to the target datastore. ### Selecting Source Tables The Source Tables Selection feature allows you to bulk create or quickly add only the relevant tables required from the source datastore to the target datastore. Based on the target datastore type, this feature automatically creates individual replications for each selected table using the source table names. For example, when both the target and source datastores are of the **SKP Catalog System** type, the feature creates **table replications**. However, if the target datastore is of the **Syniti Drive** type and the source datastore is of the **SKP Catalog System** type, it creates **File Export** replications instead. The replications created using this feature will replicate data to the target datastore using the same schema, table name, column properties, and constraints (dependencies) that are imported via the metadata scanned from the Source datastore in the Catalog module. If your Target datastore contains a Schema value, then Replicate Preview will use this default schema for all the replications created using this feature. If no schema is specified, then the Source datastore’s schema will be considered. To select source tables and bulk create replications: 1. In the Sources panel, select a source datastore and click the **Source Table Selection** icon. The Source Tables Selection dialog box is displayed with a list of tables available in the selected source datastore. 2. If you want to import all source tables into the workspace, select **Import All > Confirm**; otherwise, skip to Step 3. > [!NOTE] > Note > > Importing all tables may take some time to process (depends on the number of available tables), as it generates individual replications for each table in your workspace. 3. In the Name column, use the column filter to search for a specific source table using its unique name. 4. Select the checkboxes of the required tables. Note that the Datasource Tables label displays the number of the selected tables out of the total available tables in this source datastore. 5. Click **Create Replications** to save and create replications for the selected tables. Replications for the selected tables are created and displayed in the Replications panel. If pooled and clustered tables exist in the source system, Replicate Preview automatically selects the RFC connection types for these tables from both source and target systems to create replications. If no RFC connection type exists in the source and target datastore, Replicate Preview uses the default connection and displays an error for these replications when executed. If you want to create additional replications manually or edit an existing replication to specify filter conditions at the source, refer to the [Adding Manual Replications](/docs/configure-workspace-datastores#adding-manual-replications) section for more information. ### Adding Manual Replications Selecting the source tables in the Source datastore automatically creates separate replications for each selected table. These replications when executed, will creates target tables in target datastores with the same table and column attributes as the source tables. Source datastore’s schema will be used unless a default schema is entered while adding a target datastore. To create a replication for certain use cases (for example, move only a subset of the source table data to the target table) or specify different column attributes and names for your target table, you can add a replication manually or edit an existing replication. To add a manual replication: 1. In the Sources panel, select the required source datastore associated with the intended target datastore and click the **Add Replication (+)** button in the Replications panel. The New Replication dialog box is displayed. Note Ensure that the selected source datastore and its corresponding target datastore is displayed correctly. 2. In the Source section, tables available in the source datastore is displayed. Select the required table. 1. If required, you can filter records from the source table using the Source Filter field. For example, you can specify a condition (WHERE clause) to ensure only relevant records are inserted into the target table. > [!NOTE] > **Note** > > You don't need to explicitly include the WHERE keyword in the Source Filter field. Examples: > > - For SQL sources, `COUNTRY = 'US'` . > - For OData sources, use filter expressions such as `Status eq 'Active'` or `Status eq 'Active' and Price lt 100`. > - For MongoDB, the filter has to be in JSON format, `{'CLIENT': '100'}` . > [!NOTE] > Note > > If this replication will be included in an Orchestrate workflow of custom type, you can enter variable placeholders `{{VariableName}}` within the Source Filter field to update replication source filters dynamically. 3. In the Target section, the Target datastore is displayed. If no database or schema values are specified in the target datastore, then Source datastore’s database and schema values will be used. 1. In the Target Name field, enter the table name corresponding to the source table name. 2. To replicate by dropping and recreating the table instead of truncating the data, turn on the **Drop Target Table** toggle. > [!NOTE] > Note > > Ensure that the Append Mode toggle is disabled when using Drop Target Table during replication. Replication will fail if both toggles are enabled. 4. In the Additional Properties section, complete the following steps: 1. To specify higher preference for this replication over others, enter a priority value in the Priority field. Note The replications will be ordered and executed using the Priority value. By default, the value for each replication is set at 1000, which provides equal preferences for all replications, but ordered using the creation time of a replication. 2. To replicate data without truncating data in the target table, turn on the **Append Mode** toggle button to append new data from the source table. 3. Select **Pre-Execution** and **Post-Execution Workflows** to run if this replication is integrated with other module’s tasks in an Orchestrate workflow. 5. Click **Save**. A replication for the selected source datastore is added to the current workspace. > [!NOTE] > Note > > Refer to [Working with the Replications Panel](/v1/docs/working-with-the-replications-panel) to learn more about the Replications panel and its usage. ### Other Replication Types You can also add the following replication types: - [Orchestrate Workflow as a Replication](/v1/docs/adding-an-orchestrate-workflow-as-a-replication) - [File Import Replications](/v1/docs/adding-file-import-replications) - [File Export Replications](/v1/docs/adding-file-export-replications) ## Next Steps After creating replications, Replicate Preview automatically applies partitions, maps source tables’ fields and its datatypes to the target tables with the corresponding attributes. You must access, validate, and configure (if required) the [field mappings](/v1/docs/performing-field-mappings) and [replication dependencies](/v1/docs/configuring-replication-dependencies) before [executing replication jobs](/v1/docs/execute-replication-jobs) for the configured replications. You can begin grouping replications that are related to each other into a single group in the *Groups* tab. Grouping replications allows you to efficiently organize and manage data replication of your organization’s data for multiple use cases. Refer to [Configure Workspace: Groups](/v1/docs/configure-workspace-groups) for more information on creating replication groups and adding replications to a group. ## Related Articles - [Configure Workspace: Groups](/v1/docs/configure-workspace-groups) - [Configuring Replication Dependencies](/v1/docs/configuring-replication-dependencies) - [Execute Replication Jobs](/v1/docs/execute-replication-jobs) - [Performing Field Mappings](/v1/docs/performing-field-mappings) - [Syniti Drive](/v1/docs/syniti-drive) - [Working with the Sources Panel](/v1/docs/working-with-the-sources-panel) - [Working with the Targets Panel](/v1/docs/working-with-the-targets-panel) - [Working with the Replications Panel](/v1/docs/working-with-the-replications-panel)