Value cannot be null. Parameter name: key when comparing two databases created from DBCC CLONEDB

InfocorpInfocorp Posts: 1 New member
edited April 28, 2020 3:59PM in SQL Compare
All comparisons between databases fail when at least one of the them is a clone created with DBCC CLONEDATABASE, no matter if it is the source or target database. Based on what I've seen in other posts, I've tried with both the same AND different instances but the error keeps happening. I'm sysadmin on both instances and I'm using the latest version of SQL Compare as of today (14.2.9.1558 Professional).


Tagged:
· Share on Twitter

Answers

  • Pete_RuizPete_Ruiz Posts: 123 Silver 4
    Hello @Infocorp

    I believe we have a Support ticket open with you, just copying my reply here:

    Do you know if the database being cloned has any replication publications? We've seen this issue before when a database referenced objects that pertain replication information and don't exist in the clone because DBCC CLONE doesn't generate the system tables related to replication, such us sysarticles or sysschemaarticles.

    I hope this is helpful. Please let me know if you have questions.

    Kind regards,

    Pete Ruiz

    · Share on Twitter
Sign In or Register to comment.