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.