How can we help you today? How can we help you today?

Duplicate objects found

It appears to be the case that if i change a table to a view or vice-versa then both objects of the same name end up in TFS and then redgate:sql source control cannot tell them apart.
To resolve i have to go into TFS and manually remove the one i no longer want long-term
Is this a known issue?

eg.Duplicate objects found with name [<Schema>].[<Table>]: found objects with ids: 68516, 68933
kalo
0

Comments

8 comments

Sort by
  • Tianjiao_Li
    Hi @kalo

    Can you please confirm the full version number of your SQL Source Control? If not already, can you upgrade to the latest version (6.0.7.7122 - January 9th 2018) and test again?
    Tianjiao_Li
    0
  • kalo
    hi,

    About is saying Version 6.0.2.6908 and check for updates is saying "No updates available: You are running the latest version"
    kalo
    0
  • Tianjiao_Li
    Can you please turn on Frequent update (Help- Configure Frequent Updates) and try again?
    Tianjiao_Li
    0
  • kalo
    Hi,

    Sorry situation has not naturally arisen again until now, but this error is still being thrown

    rdi40lpmg0w1.png

    regards
    kalo
    0
  • kalo
    I am now on Version 6.1.8 and this issue is still occurring.

    If i have checked in an object name as a table and then later change the name of the table and encapsulate it into a view of the original name so that referencing objects still work, i am then prevented from checking in any changes as redgate doesn't like the duplicate objects it sees (the original table and the new view with the same name). I therefore have to spend time manually amending the items in TFS myself.
    kalo
    0
  • RichardL
    Hi @kalo

    If you have a support contract could you please send in a ticket so that this can be looked at a little faster? 

    Best

    Richard. 
    RichardL
    0
  • CaptainSensible
    We face exactly the same problem: Dropped a table and created a view with the same name, via svn.
    CaptainSensible
    0
  • CaptainSensible

    Wanted to share my solution after getting support:

    Thank you very much for the quick answer. After some more trying with your advice I found that the double was caused from another table with a very similar name. Deleting all the doubles via Tortoise svn solved the issue so it was a kind of user problem.

    CaptainSensible
    0

Add comment

Please sign in to leave a comment.