-- try
SELECT [UniqueClaimID], count(distinct ProvOrgNm) nProvOrgNm, count(*) nRows
FROM [phm_db].[dbo].[PCP2Final]
group by [UniqueClaimID]
having count(*) > 1
order by nRows desc
;

Please also read the follow up article "Logon monitoring in SQL Server and Azure Managed Instances - Adopting Extended Events"

Another enhancement to avoid the downsides of notification service queues

Question should be: why doesn't the name resolving work ?

did you check this?

How to troubleshoot the "Cannot generate SSPI context" error message

If it's on the D-drive of the azure vm and 15 seconds timeout reached, I would open a case with Azure support !

on top of the other replies:

Only a log backup marks the log file entries to be overwritten except for open transactions.

DO NOT SHRINK LOG FILES ! ( unless you performed...

Check http://sqlconjuror.com/sql-server-always-on-monitoring-script/

and

https://solutioncenter.apexsql.com/performance-monitoring-of-alwayson-availability-groups-part-1/

• This reply was modified 3 years, 11 months ago by Johan Bijnens.

have the user reboot his client pc.

Be wary for stored credentials

indeed, Jeff.

Default trace only last so long ...

Check the comments at SQLSkills article  CHECKDB From Every Angle: Using DBCC PAGE to find what repair will delete

Check sqlserver errorlogs ! ( of all involved instances ! )

Check the cluster logs !

what is the state of your servers ?

Why did it fail over ?

Is it only the...

SQL2005 doesn't have XE!

Check your default trace file or run a trace to figure it out !

Did you try this ?

Select *
, stuff(
   (
           select rtrim(T2.postcd) + ', ' 
 ...

what is the actual error and error message you are receiving ?

Everything except OS and backup related.