Hi, details first: Installed updates: edit: Problematic instance: Others two have the same number. I'm trying to install SQL CU Update SQLsERVER2019-kb5039747-X64.EXE (also tried other version - same result). After finish got error: Error.log attached: ERRORLOG.LOG Also tried to uninstall this hotfix 4298 but after deinstall service didnt start

Hello, According to your error log and MS document , Errors 912 and 3417 are generic errors associated with database upgrade script failures. And the messages preceding error 912 usually provide information on what exactly failed during the execution of these scripts. Troubleshooting and fixing these errors will require you to start SQL Server with trace flag 902 to bypass running the upgrade script . You can add this flag using SSCM as below screenshot, using cmd ; NET START MSSQL$INSTANCENAME /T902 Note: Be sure to remove -T902 from the configuration once you have resolved the issue. Please using below T-SQL to check the collation of your server instance and system databases. ---check system database SELECT name, collation_name FROM sys.databases WHERE database_id <= 4 ---check server instace SELECT serverproperty('Collation') If the collation is not same, please correct this. We can use alter database command to change this option, refer to this blog Changing SQL Server Collation After Installation to get detail command. https://www.mssqltips.com/sqlservertip/3519/changing-sql-server-collation-after-installation/ If the answer is helpful, please click " Accept Answer " and kindly upvote it.

SQL Update problem. Error: 468, Severity: 16, State: 9. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Polish_CI_AS" in the equal to operation.

Accepted answer

CathyJi-MSFT 22,206 Reputation points Microsoft Vendor

2024-08-05T06:29:10.13+00:00
Hello,

According to your error log and MS document, Errors 912 and 3417 are generic errors associated with database upgrade script failures. And the messages preceding error 912 usually provide information on what exactly failed during the execution of these scripts. Troubleshooting and fixing these errors will require you to start SQL Server with trace flag 902 to bypass running the upgrade script. You can add this flag using SSCM as below screenshot, using cmd ;

NET START MSSQL$INSTANCENAME /T902

Note: Be sure to remove -T902 from the configuration once you have resolved the issue.

Please using below T-SQL to check the collation of your server instance and system databases.

---check system database SELECT name, collation_name FROM sys.databases WHERE database_id <= 4 ---check server instace SELECT serverproperty('Collation')

If the collation is not same, please correct this. We can use alter database command to change this option, refer to this blog Changing SQL Server Collation After Installation to get detail command. https://www.mssqltips.com/sqlservertip/3519/changing-sql-server-collation-after-installation/

If the answer is helpful, please click "Accept Answer" and kindly upvote it.
Please sign in to rate this answer.
Koliński Łukasz 20 Reputation points

2024-08-05T09:04:40.69+00:00

Query result on akmodit (no problem with update)

Query result on prod2(with problems)

Will check from your link how to change collation

Koliński Łukasz 20 Reputation points

2024-08-05T09:30:31.14+00:00

Run this command:

C:\Program Files\Microsoft SQL Server\MSSQL15.AKMSSQLPROD2\MSSQL\Binn>sqlservr -m -T4022 -T3659 -s"AKMSSQLPROD2" -q"Polish_CI_AS"

And result (with errors) attached below:

change_collation.txt

Erland Sommarskog 111.6K Reputation points MVP

2024-08-05T20:57:25.51+00:00

You have succeeded to change the server collation and the collation for the system databases.

What Cathy did not tell you was that you should detach all user databases before you do this operation, because once it has changed the collation of the system databases, it proceeds with the user databases, giving up on the first error.

You should restore a backup of the databaes CDN_KNF_APLIKACJE, because it was able to make the collation change. This can cause problems, because the collation change is not carried out in a correct way. (The process is designed for system databases.)

You may also want to restore a backup of the databae CDN_AK_PROD. However, for this database, the collation change failed, and believe that there is a single transaction for the database, so this database was rolled back.

Have you tried to start SQL Server in a normal way, with out TF902? How did that go?

Koliński Łukasz 20 Reputation points

2024-08-06T08:12:37.39+00:00

I reverted the state of the machine before this script was run, then:

1.detached users databases

2.run script

result here:change_collation_DB_detached.txt

restarted server (problems with access to error log and service didn't start). After restart service run with no problems

Attached users databases

Started once again SQL ServerCU28

edit: evertything looks good. Please check change_collation_DB_Detached log if there is something to worry about.

Erland Sommarskog 111.6K Reputation points MVP

2024-08-06T21:28:57.48+00:00

Seems like you have it all working then!

There are some funny message in the errorlog, but I can't see any relation your collation mishap. They are rather due to stupidities in msdb110_upgrade.sql.

CathyJi-MSFT 22,206 Reputation points Microsoft Vendor

2024-08-07T06:02:10.0966667+00:00

Please continue with no worry.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

SQL Update problem. Error: 468, Severity: 16, State: 9. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Polish_CI_AS" in the equal to operation.

0 additional answers

Your answer