dbForge Studio. Compare schema and sync source and target databases. A special case.
1. Mapped table1 in source to table2 in target while schema compare (renamed the table in target)
2. Executed the sync script generated
3. Compared schema again to check the status after sync
Compare Result: Table1 doesn't exist in source. It's asking table2 to be dropped.
Expected result: Now both source and target have table2. it should find and match them together.
Tried...
1. Edit comparsion. It shows table2 as left unmapped.
2. Close comparsion. Reopen and try again. Now it picked up and mapped table2 to table2.
dbForge Studio for SQL Server. Compare/Sync issue when an object is renamed
-
- Posts: 1
- Joined: Fri 15 Dec 2017 07:27
Re: dbForge Studio for SQL Server. Compare/Sync issue when an object is renamed
We will investigate this issue and will answer you as soon as possible.
Re: dbForge Studio for SQL Server. Compare/Sync issue when an object is renamed
Table mapping works basing on schema mapping.
Could you please let us know whether the tables you compare belong to the same schema or not?
Also, please provide us the version of dbForge.
Could you please let us know whether the tables you compare belong to the same schema or not?
Also, please provide us the version of dbForge.