An entry with the same key already exists

Brian DonahueBrian Donahue Posts: 6,590 New member

Thanks for asking. If you set the 'Treat items as case-sensitive' option, then refresh the comparison, it should eliminate the problem.


  • I've had the same problem

    I'm trying to create a snaphsot of my production server (SQL Server 7) and I get this message. I tried numerous combinations of options. Then I noticed that there was an upgrade available which I have installed but I still get the same error regardless of the case sensitive option.

    Unfortunately this will be an urgent issue for me soon (i.e. before the end of next week!!)

    Any suggestions would be gratefully received


  • Brian DonahueBrian Donahue Posts: 6,590 New member
    I'd imagine that your server probably also has a case-sensitive collation. 'Treat Items as Case-Sensitive' will cause the collections of objects not to be indexed by object name, so this must be a special case.

    I'll have a look at the way the software stored the objects when the case-sensitive option is on and see if I can find a problem.

    Thanks for your patience.
  • I'm sure you'll be pleased to know that I have now resolved this. I came across a duplicate users name.

    The dba concerned has been suitably chastised


This discussion has been closed.