Fix Replication Extra Tables in Skyvia Database

Replication creates extra tables in the database

Overview

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 like:

dbo.Account_2ade4447_5e11_4308_9e81_5eab62d9ed52
dbo.Account_7c473919_0b04_4c82_a993_e8445843bac4
dbo.Account_8220931f_c341_45aa_a4ec_ddd3fce83936
dbo.Account_96dc6902_1dc6_413d_a206_f116f076130b

Why This Happens

These are temporary tables that Skyvia creates during Replication, where data is temporarily transferred and merged with the main table, after which these tables are deleted. Under normal circumstances, the user should not see these tables. If they are visible, there are 2 possible explanations:

  1. Replication has not finished yet - the temporary tables have not been deleted yet. When Replication completes, it will clean them up automatically.
  2. Insufficient permissions - the database user in the connection does not have permission to perform the DROP TABLE operation, so Replication cannot delete the tables after itself.

Resolution

  • If the issue is caused by insufficient permissions, grant the DROP TABLE permission to the database user used in the Skyvia connection, then delete the leftover temporary tables manually.
  • It is also recommended to update the Skyvia Agent to the latest version. 

    • Related Articles

    • Skyvia Full (Initial) Replication

      Overview 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 ...

    • Advantages of the New Replication Runtime

      Overview The new Replication runtime introduces significant improvements over the old runtime in terms of performance, flexibility, and error handling. You can enable it by selecting Use new runtime in your Replication integration settings. Key ...

    • Replication: Schema Validation Failed (Absent Columns / Redundant Columns)

      Overview 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: "Integration failed: Table 'TableName' schema validation failed: Absent columns: 'FieldName1', ...

    • Replication: MySQL Error: Row size too large (> 8126)

      Overview 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 ...

    • HubSpot: hapikey Permission Error

      Overview This error is common when working with HubSpot and indicates that the API key (hapikey) used for authentication does not have sufficient permissions to access one or more HubSpot objects. Root Causes The error typically occurs for one of the ...