I'm trying to install SSRS 2019 on an instance with existing databases created with the standard collation (SQL_Latin1_General_CP1_CI_AS) and it appears SSRS wants Latin1_General_CI_AS_KS_WS.
There are objects in those databases that use schema binding. When the SSRS installation process failed with error messages about not being able to change the collation because of schema binding I decided to create the SSRS databases manually and encountered the same issues.
Below is the database creation script and one example of the error about the schema bound object.
The instance is a sandbox, but I would still rather not have to screw around with the existing databases. Is there another way around this issue?
Thanks in advance for any suggestions you can offer.
CREATE DATABASE [ReportingServices] CONTAINMENT = NONE ON PRIMARY ( NAME = N'ReportingServices', FILENAME = N'S:\2019\Data\ReportingServices.mdf' , SIZE = 270336KB , FILEGROWTH = 65536KB ) LOG ON ( NAME = N'ReportingServices_log', FILENAME = N'S:\2019\Data\ReportingServices_log.ldf' , SIZE = 102400KB , FILEGROWTH = 65536KB ) COLLATE Latin1_General_CI_AS_KS_WS GO Msg 5075, Level 16, State 1, Line 1 The object 'dbo.name_value_pairs.name.c' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. Msg 1806, Level 16, State 1, Line 1 CREATE DATABASE failed. The default collation of database 'ReportingServices' cannot be set to 'Latin1_General_CI_AS_KS_WS'.