To be absolutely sure of correct matches, you'll need something to sequence the rows so that you know the specific order of the rows.  I added an id for that,...

Try this:

GRANT EXECUTE ON xyz.SPName TO LocalSQLaccount AS ADGroup;

SQL alerts have...

Oops,...

 Clustered index scans should definitely be adversely affected by masses of empty space in pages from deleted rows, since the scan will have to read lots more...

See if this gives you the correct totals.  I have not taken performance into consideration yet, just trying to get the correct result.

Be sure to add a date check to...

(1) Agree with ZZ.

(2) Yes, but you will also need to look at missing index stats at least, possibly cardinality data and index operations stats too.

(3) Yes, sort of.  index...

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...