Temporary tables created in SQLServer use the collation for tempdb, not the application database ------------------------------------------------------------------------------------------------ Key: HHH-3326 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3326 Project: Hibernate3 Issue Type: Patch Affects Versions: 3.2.4.sp1 Environment: SQLServer (All versions) Reporter: David Good Attachments: Dialect.java, SQLServerDialect.java, Table.java The use of temporary tables for updates in SQLServer will fail if tempdb uses a different collation to the application db. Specifically, comparisons between the primary table columns and the temporary table columns fail. It is unclear to me under what circumstances a temporary table is created, so I'm afraid no test case is attached. I do however attach modified versions of the following classes: org.hibernate.mapping.Table org.hibernate.dialect.Dialect org.hibernate.dialect.SQLServerDialect These resolve the issue, but the solution may not be the most optimal possible, as it involves intervention in a specific position (between the datatype declaration and any nullability clause) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira