Error synchronizing database with red gate SQL compare

Today I was synchronizing two database with red gate sql compare, newer database has 6 more additional view, but the sync script failed with some errors. One of the view is called MatterKnowledges and the script return error “matterknowledges” already exists, even if the destination database has no such view. The problem originates from the fact that the view (SQL2000) was create with a different name and then renamed to MatterKnowledges. The solution to the problem was dropping and then recreate the view on the original database, now all works ok.

Alk.

Published by

Ricci Gian Maria

.Net programmer, User group and community enthusiast, programmer - aspiring architect - and guitar player :). Visual Studio ALM MVP

One thought on “Error synchronizing database with red gate SQL compare”

  1. This is an annoying SQL Server problem with objects that are renamed using sp_rename. The system tables in SQL Server store inconsistent information after such renames (the text of the view, procedure, etc is not updated). The latest version of SQL Compare (version 6.1) detects such inconsistencies and fixes the database objects (views, stored procedures, etc.) With this version you should not experience the above problem.

    Regards,
    Andras

    Andras Belokosztolszki
    Red Gate Software

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.