If it can't be done with unique constraint/index. Maybe a trigger?

We didn't hit that error. Catalog property is still ntext, Tempcatalog property is nvarchar(max). Collation Latin1_General_100_CI_AS_KS_WS. Instance collation Latin1_General_CI_AS.

The article seems correct.

Is this a native SSRS 2012 reporting to native 2019?

(reason: Sharepoint integrated is mentioned in https://stackoverflow.com/questions/44277492/ssrs-reporting-service-gives-an-error-the-found-version-is-163-the-expected-v )

Have you tested SSRS 2019 before restoring Reportserver-database + restore...

You can trace some with extended_events

ADD EVENT sqlserver.error_reported(

ACTION(sqlserver.client_app_name,sqlserver.client_hostname,sqlserver.client_pid,sqlserver.database_id,sqlserver.database_name,sqlserver.nt_username,sqlserver.plan_handle,sqlserver.request_id,sqlserver.session_id,sqlserver.session_resource_group_id,sqlserver.transaction_id,sqlserver.tsql_frame,sqlserver.username)

WHERE ([severity]>(10))),

The backup probably hits the iops limit of your storage account during backup https://docs.microsoft.com/en-us/azure/virtual-machines/disks-performance.

http://2forward.eu/azure-vm-and-disk-throttling-alerting/

seems to have a way to generate an alarm when your azure vm is being disk-throttled

No clue at the moment.

What version of Azure Data Studio are you using?

There was a bug https://github.com/microsoft/azuredatastudio/issues/8509

Mostly 2 years after a major release. Luckily we are in control of most programs and the ERP was greenfield. Azure is causing an increase of upgrade tempo

The older version...

Usually I start with select top (1) * from table1, adding joins, where's ... later on. Refining * is usually done later on

Glad it is resolved, thanks for the solution

Can't see the latest screenshots.

With the validation error 'MSSQLSELSERVER' exists you could try a repair install

Or try to install a named instance instead of the default instance (which gets the...

Likely there is some WMI corruption on your system that must be fixed first. ( error mentions wmi server, and the first error was regarding countername)

From what I can find on the internet they fixed lodctr /r in system32 by running it in syswow64 and then back in system32

https://answers.microsoft.com/en-us/insider/forum/all/possible-performance-counter-problem-on-win10/3a5c22cb-1425-4d26-99e7-4ec46940b9a1

Do you have a question? It reads like a statement

That's an unusual error. I believe your windows wmi performance counters are corrupt

Cannot load Counter Name data because an invalid index https://success.trendmicro.com/solution/000152298

Recommendation: uninstall sql 2019

Fix Wmi performance counters https://docs.microsoft.com/en-us/troubleshoot/windows-server/performance/rebuild-performance-counter-library-values

Reboot...

Still finding ntext datatypes in sql server reporting services 2019 🙁