4

I just installed SQL Server 2019. Unfortunately I didn't notice the collation while installing. Following are the collations:

SELECT name, collation_name
FROM sys.databases  
name collation_name
master Latin1_General_CI_AS
tempdb Latin1_General_CI_AS
model Latin1_General_CI_AS
msdb Latin1_General_CI_AS
ReportServer Latin1_General_100_CI_AS_KS_WS
ReportServerTempDB Latin1_General_100_CI_AS_KS_WS
ApplicationDB SQL_Latin1_General_CP1_CI_AS
use ApplicationDB    
GO 
SELECT SERVERPROPERTY(N'Collation')

SQL_Latin1_General_CP1_CI_AS

The application recommends that the database to be SQL_Latin1_General_CP1_CI_AS, but they're unsure about the system databases as they're not database experts. Will there be any consequences. We would be running SSRS reports to pull data from the application database. Will this be an issue? I'm confused

3
  • afaik, the collation on system databases shouldn’t effect the behavior of your applicationDB and it’s functionality. As long as your reads and writes are constrained within the database then you are fine. May 13 at 2:42
  • 3
    @SivaDasari TempDB uses instance collation, and that might cause unexpected issues.
    – vonPryz
    May 13 at 5:24
  • @vonPryz you are right and thank you for sharing those sources. Which needs to be verified from the application whether explicit COLLATE is specified for tempdb operations. May 13 at 6:43

1 Answer 1

0

This issue can be solved using database repair script. I have faced similar kind of issue. Try using provided link

https://www.sqlservercentral.com/articles/change-collation-at-instance-level-through-rebuild-databases-in-sql-server-2017

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy