Options

Difference between name exposed / internal

buckleybuckley Posts: 69
edited May 26, 2006 4:04AM in SQL Compare Previous Versions
This gives me sync trouble :

red.jpg

The difference in name makes redgate think the object isn't at the other server so it wants to sync it in vain.

Is this a known problem. I've seen it happen a few times before.
Looks like sql server is inconsistent.
· Share on Twitter

Comments

  • Options
    buckleybuckley Posts: 69
    I found the cause of the sync problem.

    Seems like if you rename a view (maybe other objects too) in SQL EM then the internal name of the object isnt updated. Hmz

    You can check this if you rename a view and tell SQL EM to geneterate the sql script. This is a source for confusion I think. Is it a SQL server bug?
    · Share on Twitter
  • Options
    buckleybuckley Posts: 69
    bump
    · Share on Twitter
  • Options
    James MooreJames Moore Posts: 252
    You are indeed correct - this is an inconsistency caused by using sp_rename. The stored proc is renamed but its definition SQL is not - SQL Compare uses the definition SQL and thus this is where the problem arises - it can be resolved as you correctly point out by updating the definition SQL.

    - James
    --
    James Moore
    Red Gate Software Ltd
    James Moore
    Head of DBA Tools
    Red Gate Software Ltd
    · Share on Twitter
Sign In or Register to comment.