Hi @Limiw ,
I am aware of the difference of SCOR (SCORCH) and SCOM ;-)
If you don't use SCOM at the moment and no plans for using SCOM in the future together with SCOM there is no reason to think that much about the SQL server collation in my opinion.
You can bypass this warning message and continue to install using the SQL_Latin1_General_CP1_CI_AS. Further, the SQL_Latin1_General_CP1_CI_AS collation was not listed as a supported collation on the Language Support for System Center 2012 - Service Manager page on the TechNet Library. The required collation for SCSM per the documentation currently is Latin1_General_100_CI_AS (note the 100).
The information for SCOR and SQL collation you will find here:
Orchestrator supports SQL_Latin1_General_CP1_CI_AS for collation. The installation wizard uses SQL_Latin1_General_CP1_CI_AS as the default collation to create the orchestration database.
For SCSM the SQL collation SQL_Latin1_General_CP1_CI_AS
is supported as well.
Source: https://learn.microsoft.com/en-us/system-center/scsm/sm-languages?view=sc-sm-2016
I am aware of some System Center environments running different SC components in the same SQL instance with the same SQL collation without any problem.
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten