Effect of collation change on tempdb space consumption

  • If the collation for one database is different from all other databases on a SQL 2008 Server, will it impact the tempdb space consumption?

    I understand that queries and joins may fail due to the collation difference and it could be handled using COLLATE database_default option.

    Question is will collation difference anyway increase the amount of tempdb space consumption during joins / SORT/aggregate operations?

  • The worst case is that it could require more space due to a collation that forces everything to a Unicode comparison based on the data types, but it should not be a tremendous amount of difference. If you are making comparisons between Unicode-Unicode values, you'll need the same space.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply