DB Compare crash
Brian Donahue
Posts: 6,590 Bronze 1
Hi Gonzalo,
Thanks for your post.
You can usually make this error disappear by changing the 'Treat Items
as case-sensitive' option in the software. For servers with case-sensitive
collation, this will make SQL Compare behave properly and allow objects with
different case-sensitive names to be compared.
Regards,
Brian Donahue
Red Gate Technical Support
"Gonzalo" <gonzalos@marketingconcepts.com> wrote in message
news:bfA4RPUiEHA.3144@server53...
> When comparing 2 databases, I get the following error:
>
> Item has already been added, Key in dictionary: "[dbo].[usp_XXXXX]" key
bein
> added: "[dbo].[usp_XXXX]"
>
> Then I click ok and the SQL compare does not do anything.
>
> I just got this tool. So Iam afraid I am doing something wrong. However it
> should give a better error.
>
> Please advice as I need to make changes to my live DB.
>
>
>
>
>
Thanks for your post.
You can usually make this error disappear by changing the 'Treat Items
as case-sensitive' option in the software. For servers with case-sensitive
collation, this will make SQL Compare behave properly and allow objects with
different case-sensitive names to be compared.
Regards,
Brian Donahue
Red Gate Technical Support
"Gonzalo" <gonzalos@marketingconcepts.com> wrote in message
news:bfA4RPUiEHA.3144@server53...
> When comparing 2 databases, I get the following error:
>
> Item has already been added, Key in dictionary: "[dbo].[usp_XXXXX]" key
bein
> added: "[dbo].[usp_XXXX]"
>
> Then I click ok and the SQL compare does not do anything.
>
> I just got this tool. So Iam afraid I am doing something wrong. However it
> should give a better error.
>
> Please advice as I need to make changes to my live DB.
>
>
>
>
>
This discussion has been closed.
