Advantages of the New Replication Runtime Compared to the Old Runtime
The new replication runtime offers several key advantages:
• Object-level LastSyncTime, enabling incremental replication for each object
• New runtime modes: Standard, Resync, and Resync on Demand
• Improved performance by removing direct ID checks and foreign key constraints
• Enhanced error isolation (errors are logged per object instead of halting the entire integration)
• Advanced features: History Mode, Nested Objects (stored as JSON or in separate tables), and Data Hashing
You can enable it by selecting Use new runtime in your Replication integration settings.
Also, more details are available at the links below in our Recent Releases section:
April 2020 Engine Improvements
January 2024 New Runtime & Features
Related Articles
🔁 Skyvia Full (Initial) Replication
Full Replication creates a complete copy of your source data in the target database. Use it for the first replication run, after schema changes, when refreshing all data, or if you encounter duplicate records. Requirements Valid Source and Target ...
Replication: Table '...' Schema Validation Failed (Resolving 'Absent Columns' and 'Redundant Columns' Errors)
If you encounter the following errors in an integration, it means the schema of your data source no longer matches the schema Skyvia has cached: Error: "Integration failed: Table 'TableName' schema validation failed: Absent columns: 'FieldName1', ...
Replication creates extra tables in the database
In some cases, as a result of Replication, in addition to the main tables (for example, dbo.Account ), empty additional tables are created in the database with names of the following types: dbo.Account_2ade4447_5e11_4308_9e81_5eab62d9ed52 ...
What is LastSyncTime in Skyvia
What is LastSyncTime? LastSyncTime is the point when Skyvia last successfully transferred data during a Replication or Synchronization. It helps Skyvia remember what data has already been delivered, so next time, only new or updated records are ...
Replication: Error: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In the current row format, the BLOB prefix of 0 bytes is stored inline.
When performing replication to MySQL you can encounter this error: An error occurred while creating table 'Invoice'. Error: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is ...