Unless your table is named "sol(nolock)", I would avoid using NOLOCK.  It is in my coding standards that NOLOCK should be avoided except where potential data inaccuracy is acceptable...

Note, too, that the OP did not indiscriminately use NOLOCK everywhere.

In fact, it was used on only 1 table out of 9 (or so).

To me, that is exactly the way...

And I agree 110% with pietlinden on the NO LOCK hint.  I would avoid using NOLOCK.  It is in my coding standards that NOLOCK should be avoided except where...

"The result is"

For you, but not for us!  We don't have access to your tables nor do we know anything about them.  We need actual usable data to test with,...

Would it be feasible for you to use a different SQL Server Alert for each silo?  That is, the Alert would be the same except for silo name, but you...

When you plan to rebuild/reorganise an index you need to answer the main question:

What happens next?

Massive DELETEs on the table imply that there are as massive INSERTs.

What happens...

I tend to agree with you there, I think it's a type of bug as...

Thank you ScottPletcher, your method worked. The query was executed on remote server "as is". The only downside of this method is inability to use parameters. However, this...

I have trouble even imagining the business or technical case where I'd ever design a table to have massive deletes all over the table at the...

Yes... I'm well aware (and very thankful) that a given job can only be run once at a time.  The concurrency I'm talking about is when you have...

Yeah, I didn't go into deep details in the initial postings.  Didn't seem necessary.  I guess it was.  I have trouble even imagining the business or technical case where I'd...

First of all,...

• This reply was modified 5 years ago by ScottPletcher.
• This reply was modified 5 years ago by ScottPletcher.

Heh... lordy... never mind.  Nothing has changed in the last decade.  Jeffrey Yao has an article on the subject.  These aren't what I call "easy" methods and some...

• This reply was modified 5 years ago by ScottPletcher.

Personally, I'd remove SQL and re-add with the desired collation.  Changing collations can be tricky, esp. on the master db.

We already keep 1 month of backup on drive and anything above that should transfer to shared backup network and that is...