CLR Assembly comparison must always be case-sensitive
jstangroome
Posts: 26
We recently made some changes in our database to a CLR assembly that involved some case-only changes to the namespace and some class names. SQL Server 2005 seems to be very picky that all CLR references are case-sensitive regardless of database collation settings.
As such, the script generated by SQL Compare 5.1 used the case of the old (destination) database assembly objects when recreating types and functions that had been updated in the new (source) database. The SQL script failed.
I enabled the "Treat items as case sensitive" option in SQL Compare and the script then worked correctly. I believe that CLR assembly objects should always be treated as case sensitive regardless of the SQL Compare option.
As such, the script generated by SQL Compare 5.1 used the case of the old (destination) database assembly objects when recreating types and functions that had been updated in the new (source) database. The SQL script failed.
I enabled the "Treat items as case sensitive" option in SQL Compare and the script then worked correctly. I believe that CLR assembly objects should always be treated as case sensitive regardless of the SQL Compare option.
This discussion has been closed.
Comments
Many thanks for your feedback we will consider this for future releases.
Regards,
Jonathan
-Project Manager
-Red Gate Software Ltd