We seem to have gone backwards with TOAD 6.5 unfortunately.
When ever I am wanting to alter a table in my database (either production or test), I am now getting Collation errors
Cannot resolve the collation conflict between “SQL_Latin1_General_CP1_CI_AS” and “Latin1_General_CI_AS” in the equal to operation.
I am not getting these errors in either Toad 6.1 or SQL Server Management Studio 2005.
I have no choice now but to go back to Toad 6.1 for my work, as it’s hampering our ability to use our databases effectively.
Please fix urgently.