I wouldn't activate lock pages in memory SQL Server Max Memory Setting with Lock Pages in Memory (mssqltips.com)

The pagefile is rather for unexpected events, otherwise it has too few memory....

Thanks for the updated funtion

Also curious for other opinions

Since you only have one pair of drives I would keep it on a single partition with you can extend when needed.

For the pagefile I would...

The FTP-transfer is still binary ? (corruption with non-binary transfer)

What is the oldest open transaction ? DBCC OPENTRAN

Apparently Script: open transactions with text and plans - Paul S. Randal (sqlskills.com) has a script to show open transactions

SCOM 2019 SSRS would refuse to install  because the version was too high (it needed the RTM SQL Server (sigh)). I'll try it again on my laptop  (uninstall sql, install...

Maybe farfetched but is your sql server still RTM? I had problems with SCOM 2019 installation when the sql server was already patched and the "versions" didn't match (had to...

Are the sql server files excluded from antivirus?

Does it relate to backup times (more stress on io) / higher cpu usage ( certain batch with lot of iops)?

https://docs.microsoft.com/en-us/sql/relational-databases/errors-events/mssqlserver-833-database-engine-error?view=sql-server-ver15

You might try https://social.technet.microsoft.com/Forums/en-US/c535ebf3-18a0-430d-9a1a-9184182dd946/ssrs-2017-rc-1-cant-start-up?forum=sqlreportingservices

Found one with a youtube movie https://joeschoice.com/sslandmssql/

Can't see your screenshot.

As an alternative you can import the certificate using the mcc certificate snapin

https://codekabinett.com/rdumps.php?Lang=2&targetDoc=create-install-ssl-tls-certificate-sql-server

It might be need to assign read permissions on the certificate in order to be...

No more named SSRS instances since SQL 2017 https://itsalljustelectrons.blogspot.com/2018/01/Installing-SSRS-2017.html

• This reply was modified 4 years, 8 months ago by Jo Pattyn.

sqlsni.trace seems to be removed in CU8 probably for fix 13671396 XEvent sqlsni.sni_trace does not fire unless sqlsni.trace is enabled in SQL Server 2019.

Thanks to stummsft for a helper function

Solved: On SQL2019 it's called sqlsni.sni_trace instead of sqlsni.trace

Test before you try this

Now it is more clear (misread domainy). You want to change the domain of the client and make sure the acces to the original sql servers...