Keep a reporting copy of an ERP table current without a custom script.
A Data Sync profile keeps a target table in step with a source table, one way or both ways, on a schedule, with every run recorded.
Reports should not run against the ERP's live tables, and a hand-written copy job is one more thing to maintain. You want a reporting table that is current, and proof of what changed.
Modules. Database module.
Edition. DataBridge Server. Desktop does not run replication.
A real DataBridge screen, with sample data from a demo instance.
How DataBridge does it.
Each step names the feature as it appears in the product.
- Step 1
Two connections
The source login needs only SELECT. The target login needs SELECT, INSERT and UPDATE, plus DELETE if the profile deletes rows.
- Step 2
Sync profile
Choose One-way, Reverse or Bidirectional, name the key columns, and read the whole table or a narrower SELECT. The write side must be a real table.
- Step 3
Change detection
Full compare, Timestamp (a rowversion column is the most reliable on SQL Server), Row hash, or SQL Server Change tracking.
- Step 4
Preview and Validate
Preview counts what would change and writes nothing. Validate confirms both sides are reachable and the settings work.
- Step 5
Schedule and history
Use the same schedule picker as jobs. Each run records rows inserted, updated, deleted and in conflict.
- Step 6
Conflicts
A bidirectional profile needs a last-modified column on both tables and a rule: Source wins, Target wins, Last write wins or Manual review.
What this does not do.
- Data Sync works between two database tables. To move data to or from a file, an SFTP server or an API, use Transfer.
- Reads use the database's default isolation level and never NOLOCK. Full compare and Row hash read the whole source table every run, so schedule them off hours.
- Change tracking is for SQL Server sources only.
Related pages.
Try the parts that are free today.
The free browser edition needs no sign-in and never uploads your files.