How to Setup Data Lake Sync

Created by Robert Cross, Modified on Tue, 15 Jul, 2025 at 7:57 AM by Robert Cross

Setting Up Data Lake Sync: A Step-by-Step Guide

Data Lake Sync allows seamless data replication from Infor’s Data Lake to your external systems. This setup ensures you can access, analyze, and act on your enterprise data using your preferred tools. This guide outlines the exact steps to set up and configure Data Lake Sync for your organization.


Step 1: Create the Required User in Infor Portal

Begin by creating a dedicated user in the Infor Portal. Please use support@datalakesync.com as the username and email address. Assign the following security roles to enable appropriate access and administrative capabilities:

  • DATAFABRIC-SuperAdmin

  • DATAFABRIC-User

  • DATALAKE-DataAdministrator

  • DATALAKE-SystemAdministrator

  • DATALAKE-User

  • IONAPI-Administrator

  • IONDeskAdmin

  • IONDeskOAuthGenerator

  • IONDeskSecurityAdmin

These roles ensure the user can configure data flows, manage ION APIs, and securely access the Data Lake and related components.


Step 2: Identify Tables to Synchronize

Prepare and provide a list of Data Lake tables you want to replicate. This list should include the full table names, including prefix. E.g. WFM_Employee, csi_item_mst, LN_tdsls400, M3_CUSTMA. 


If you'd like to use a standard set of base tables, please let us know and we'll provide a base set of tables for your system. 


Step 3: Define Data Refresh Frequency

Specify the initial sync schedule to control how frequently data is synchronized to your destination system. You'll need to provide:

  • Frequency Type: Choose from Daily, Hourly, or Minutely

  • Frequency Interval: Applicable for Hourly and Minutely (e.g., every 15 minutes)

  • Start and End Time: Define the operating window (same value for Daily)

  • Timezone: Indicate the timezone for the schedule

  • Days of Week: If the sync should not occur daily, list applicable days (e.g., Mon–Fri)


Step 4: Destination Database Details

Provide detailed connection parameters for the external database or destination system where the data will be replicated. Required information for SQL Server includes:

  • Server Hostname (e.g., db.companydomain.com)

  • Database Port (default: 1433 for SQL Server)

  • Database Name

  • Schema Name (target schema where tables will be written)

Ensure the schema is properly created and ready for data ingestion. For other destination types, please provide appropriate information. 


Step 5: Allow External Access from Data Lake Sync

To establish the connection, the Data Lake Sync service must reach your database server. This requires:

  • Creating a firewall rule or access exception to allow inbound traffic from the Data Lake Sync IP address

  • Verifying routing rules and VPN configurations, if applicable

You must submit a Data Lake Sync support request to obtain the source IP address to be whitelisted.


Step 6: Set Up Authentication on the Destination System

Provide appropriate user credentials to allow Data Lake Sync to insert and update data. For SQL Server:

  • Use a SQL-authenticated user (not Active Directory authentication)

  • Ensure the user has full privileges on the target schema:

    • INSERT, SELECT, UPDATE, DELETE, CONTROL

For other database types (e.g., PostgreSQL, Oracle), adjust the permissions accordingly based on their privilege model.


✅ Final Checklist

TaskStatus
User created in Infor Portal with correct roles
List of Data Lake tables provided
Refresh frequency and schedule defined
Destination database details submitted
Firewall rules updated for Data Lake Sync IP
Authenticated database user provisioned

Once all steps are complete, you can create a support ticket to complete the Data Lake Sync connection.


Need help designing the right sync schedule or schema strategy? Reach out to OrangeQuery early in the process to align on data use cases and load expectations.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article