IDERA strives to ensure our products provide quality solutions for your SQL Server needs. The following known issues are described in this section. If you need further assistance with any issue , please contact IDERA Support.
IDERA SQL Comparison Toolset 7.1 removes Azure v12 support for assemblies and CLR objects including procedures, functions, triggers, types etc.
IDERA SQL Comparison Toolset includes a number of options that can cause the following issues:
LOC_TX.g_1835_ck
LOC_CA.g_1835_ck
LOC_TX
table on the left database are compared with those of the LOC_TX
table on the right database. Constraints of LOC_TX
and LOC_CA
are not mixed together.To some users, it appears as if the Select All / Clear All feature in the comparison grid does not work properly. An object still can appear in the synchronization script even after being unchecked in the comparison grid. This behavior is by design and has to do with the dependencies in the database. To ensure that an object is excluded permanently, the user must uncheck the comparison option Include dependent objects.
Some users may see an error occurring during object pairing before the schema comparison. This issue usually results from a database created with case-sensitive collation and containing objects with the same name but different case, such as Employee and employee. Note that while this error is triggered, IDERA SQL Schema Compare does continue to compare the databases. However, from the set of objects with the same name, only one of them is compared and the remainder is ignored.
Total compare from data to schema IDERA SQL Comparison Toolset. Learn more > > |
IDERA Website | Products | Purchase | Support | Community | About Us | Resources | Legal |
---|