Error comparing with a database restored from a backup of a database created with DBCC CLONEDATABASE

Hello. 

We have restored a database backup in our development environment. The original database backup was created from a database (in production environment) who was created using the “DBCC CLONEDATABASE” command. 

When we compare the database we  have created in our development environment with the production original database we are receiving the error in the next picture:


¿How we can solve this issue?

Thanks.

Answers

  • Good Afternoon!
    Can you confirm what version of SQL Compare/Data Compare that you're seeing this under? Can you also confirm the version of SQL Server instances involved between the development and production environment?

    Sean Quigley | Product Support Engineer | Redgate Software

    Have you visited our Help Center?





  • AnaSLAnaSL Posts: 5 New member
    Good morning Sean,
    The SQL Compare version I am using is 14.0.7.13517 Standard. Both databases are in the same instance, SQL Server version 12.0.5000.0.
  • AnaSLAnaSL Posts: 5 New member
    Good morning, do you have any update on this?
    Thanks.
  • squigleysquigley Posts: 188 Gold 1
    Good Afternoon!
    Apologies for the long wait on the reply, unfortunately we lost track of this due to system issues on our end.
    I have a created a ticket for you so that we can continue to investigate this issue in further detail.
    Thanks!

    Sean Quigley | Product Support Engineer | Redgate Software

    Have you visited our Help Center?





  • squigleysquigley Posts: 188 Gold 1
    After some back and forth with AnaSL on the ticket we were able to pinpoint the cause of the issue. The cloned database involved had some replication publications and the command DBCC CLONE doesn't generate the system tables related to replication, such us sysarticles or sysschemaarticles, which were used in view sys.sql_expression_dependencies, that's what caused the error. It contains information about objects which doesn't exist in the cloned database.

    Unfortunately at this time SQL Data Compare doesn't have a way to account for this discrepancy.

    Apologies for the inconvenience that this brings.

    Sean Quigley | Product Support Engineer | Redgate Software

    Have you visited our Help Center?





Sign In or Register to comment.