Home Forums SQL Server 2014 Development - SQL Server 2014 DOES COLLATE DATABASE_DEFAULT CAUSE PERFORMANCE ISSUES AND HOW DO I GET AROUND IT? RE: DOES COLLATE DATABASE_DEFAULT CAUSE PERFORMANCE ISSUES AND HOW DO I GET AROUND IT?

  • February 5, 2018 at 1:40 am

    #1978509

    carolyn.foster - Tuesday, January 30, 2018 7:31 AM

    I am updating an existing SP to point to a different database created outside of my control.  Nearly every join in the code brings back a collation conflict error so I have changed the joins to COLLATE DATABASE_DEFAULT but now the code is running ridiculously slow and filling up TEMPDB - can you suggest any other way of resolving the conflicts?

    Yep, Collation could sometimes cause some misreads by the application. Due to this unnecessary table / index scans would happen which then result into performance issues. Also when working with different collations, any objects stored in the tempdb database can cause issues.

    We can choose a collation which we can use when setting up SQL server, so that the same can be used for all your your databases and char columns. Again easier said than done...😀😀😀