@staticlibs Facing below issues in WiltonDB transfer GUI tool (wdb_transfer). Could you please help us?
- During the transfer of data's using the tool, getting the below issue,
Error = [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]duplicate key value violates unique constraint "babelfish_view_def_pkey"
This was already been discussed sometimes back here, but I would like to convey you that this happens for a table and when re-trigger migration for the same issue table, it gets succeeded again. This occurs for a average of 100 tables, one table gets issue and data migration stopped. Can you share your view on this?
-
Data migration was not fully complete, For example a employee table in sql server had 248 records, but the transfer tool migrated only 213 records, not sure why rest of 35 records not transferred. any idea on it?
-
Important Question - IDENTITY column not works in expected form in babelfish or postgreSQL after data migration. For example employeeId in employee table is identity column, the sql server had 100 records where the last identity sequence value is 100. After migration to postgreSQL, when trying to insert record to employee table, it not starts with 101 sequence, rather it was different like around 20. This is more important because we wanted to transfer the data and start sequence on top of it. Is there a way to fix this issue?
@staticlibs Facing below issues in WiltonDB transfer GUI tool (wdb_transfer). Could you please help us?
Error = [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]duplicate key value violates unique constraint "babelfish_view_def_pkey"
This was already been discussed sometimes back here, but I would like to convey you that this happens for a table and when re-trigger migration for the same issue table, it gets succeeded again. This occurs for a average of 100 tables, one table gets issue and data migration stopped. Can you share your view on this?
Data migration was not fully complete, For example a employee table in sql server had 248 records, but the transfer tool migrated only 213 records, not sure why rest of 35 records not transferred. any idea on it?
Important Question - IDENTITY column not works in expected form in babelfish or postgreSQL after data migration. For example employeeId in employee table is identity column, the sql server had 100 records where the last identity sequence value is 100. After migration to postgreSQL, when trying to insert record to employee table, it not starts with 101 sequence, rather it was different like around 20. This is more important because we wanted to transfer the data and start sequence on top of it. Is there a way to fix this issue?