Page 1 of 1
DBForge data compare - Exclude column mask not working?
Posted: Tue 31 May 2016 15:27
by ccairns
Hi,
Testing dbForge datacompare for Oracle and having trouble getting the column exclude mask to run. Rows with only the excluded column values different are being highlighted.
Ignore Case: True
Column name: VERSION
Masks tried: VERSION, version, version*, VERSION*, *VERSION*, VERSIO*
Is there any special trick to getting columns excluded from the comparison?
Thanks
Chris
Re: DBForge data compare - Exclude column mask not working?
Posted: Tue 31 May 2016 16:42
by ccairns
Got closer, by manually excluding the VERSION column from the mapping the rows showed as properly identical/different. (I think automap didn't work because no pre-defined primary key on the test database) However on rows that triggered as missing (properly), the excluded comparison column was also excluded from the insert statement, which caused the sql to fail as the column was mandatory.
Is that intended behaviour that exclusion from comparison also excludes from insert when the row is copied to the target database?
Re: DBForge data compare - Exclude column mask not working?
Posted: Thu 02 Jun 2016 13:21
by alexa
The columns that were specified for the 'Ignore columns by mask: *ColumnNŠ°me*' option will be excluded from comparison and synchronization. Obviously, if they are set as a key column, the server will not skip the error when executing the Insert instruction due to being not possible to add a row with identical or NULL value in the key column.
So, you can exclude any columns from comparison as well as define any comparison key. However, there are restrictions on synchronization that are conditioned by the table structure.