Thank you for the remark.

I'll remove it from my signature.

Strange indeed.

Did you replay it ( e.g.using the free PlanExplorer  )

Test  ( disregard )

Indeed.

Fingers crossed

without a doubt: "The Bare Necessities (from The Jungle Book)"

altough not a best practice, dynamic sql will be about the only way to help you out

ref: dos-and-donts-of-dynamic-sql 

btw: Where is the where clause of your query ?

Export csv and move to central share to be picked up by central inventory server.

We only monitor specific instances ( 100+ instances )

General /find on our network would cause management...

We export this data to a central file location and then have our central inventory server pickup and process those files.

SELECT SERVERPROPERTY('ServerName') AS [ServerName]
   ...

ah, that is indeed how I run most of my Posh scripts with sqlagent.

Keep in mind a unique constraint is materialized as a unique index.

You'll need to contact your devs and get their accord.

Don't just disable/drop without consent

Nice one 🙂

I would restart the full server ( OS )

I've seen this happening on some of our SQL2008R2 instances on very rare occasions

create-an-html-report-on-the-status-of-sql-server-agent-jobs

On top of Steve's reply:

Make an inventory of all "non-default" collations in your instance / db  and find the reason for that/those.

In many cases it is unintentional or someone scripted...