I think in

rsreportserver.config

SSLCertificateConfiguration

• This reply was modified 4 years, 2 months ago by Jo Pattyn. Reason: misread, is about ssrs certificate
• This reply was modified 4 years, 2 months ago by Jo Pattyn.

Can't help you with it. Are you using the latest SSMS?

What do you mean by "there is a small difference in DNS between VM and SQL hostname"

What software do you use for the connection?

Do you connect using the fully qualified...

Haven't read it, but I wouldn't buy a book regarding SQL 2012 today.

The current version is 2019 and there was a major change with version 2016, you would miss out...

The update query still takes an exclusive lock to make the necessary modifications.

Under pessimistic locking your select query waits till the exclusive lock is released.

Without the tabledefinitions ,query, queryplants it...

If jobdatestart is a date or datetime, compare it with a date(time) instead of a string regarding [jobdatestart] > '6/1/2021'

Wat are the instance/database collactions of the 2012 reporting server? Reinstall the 2019 server using the 2012 collations?

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