I have different collation in my database then on the server.
Every time when i define temp table inside query I also set its collation to database collation - to prevent collate conflicts.
But what happens when SQL use temp database internally? From execution plan it sometimes split results into tempDB, and when executing joins or when sorting data - for sorting it uses temp db, for row versioning at snapshot isolation level,... and for all other operations when tempDB is used. Does it use tempDB collation and then converts data back to database collation to go further in execution plan?
What is the performance impact in cases like this?
All column data types are varchar and not nvarchar. Does it has some impact on mixed collation problems?
br, Simon