SQL Server crash related to tempdb collation - by Robert Heinig II

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 776579 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/15/2013 2:54:03 AM
Access Restriction Public


In SQL 10.50.4000 a session crashes in a context involving differing collations on tempdb and the current db. Adding COLLATE DATABASE_DEFAULT to the temp table fields prevents the crash.

I've always thought that COLLATE DATABASE_DEFAULT should be the implicit default for all char fields in temp tables, which would probably also fix that years-old bug with SSMS' Securable pages...
Sign in to post a comment.
Posted by Umachandar [MSFT] on 2/14/2013 at 12:26 PM
Hello Robert,
I apologize that the bug was closed as no repro. Typically, we investigate issues (unless it is serious enough) in the latest version of SQL Server and then go from there. In this case, our developer tested the repro in SQL Server 2012 to see if the problem exists there & close the issue as no repro since it was fixed. He did try the repro in SQL Server 2008 R2 also to verify the problem but as I said earlier we decided not to pursue a fix there. Sorry, if this caused any confusion.

Umachandar, SQL Programmability Team
Posted by Robert Heinig II on 2/13/2013 at 11:47 PM
That's very good. Only - please do not mark a case as not reproducible first and explain several hours later. I already put in bandwidth and hours to build a demo VM.
Posted by Umachandar [MSFT] on 2/13/2013 at 2:36 PM
Hello Robert,
We looked at this and the problem has been fixed in SQL Server 2012. If you require a fix for older versions then you need to contact CSS.

Posted by Umachandar [MSFT] on 1/18/2013 at 11:51 AM
Thanks for providing us the min-dump files. We will see if we can investigate the problem and identity the root cause using that.

Posted by Robert Heinig II on 1/18/2013 at 2:30 AM
Zip attached, hope you don't mind I flagged them MS-Only.
Posted by Umachandar [MSFT] on 1/17/2013 at 12:51 PM
Can you please attach the mini-dump files when you hit the exception? These files will be the SQL Server LOG directory.

Umachandar, SQL Programmability Team
Posted by Robert Heinig II on 1/16/2013 at 8:07 AM
No need to call CSS - workaround included :)
Also, sorry, for erroneous wording: It's not the service that crashes, it's just the one spid. I had unexpected recovery messages in my log, but those were unrelated, forgot to check the exact timestamps. Will fix above for future readers.
Posted by Umachandar [MSFT] on 1/15/2013 at 2:23 PM
Hello Robert,
Thanks for reporting the issue. Did you call CSS regarding the problem to troubleshoot this further? We will take a look at your repro & investigate the issue.

Umachandar, SQL Programmability Team