This ends up being a very complex task.  There are a number of threads about it on this site.

Here's a doozy (from history): Claus Philipp Maria Justinian Schenk Graf von...

An alternative:

SELECT
    Field0,
    CASE WHEN Field1_with_Field4 <> '' THEN Field1_with_Field4 ELSE Field1_without_Field4 END AS Field1,
    CASE WHEN Field1_with_Field4...

USE [DB_XYZ];

GRANT EXEC TO [MyDomain\User_1]

That includes system procs, of course.  If you prefer, you can do this:

GRANT EXEC ON SCHEMA::dbo TO [MyDomain\User_1]

I might be misinterpreting what you're saying above but,...

I've started creating a separate deadlock extended event myself.

Here's an example of how to create a deadlock ext event.  Naturally your WITH options may vary.  You can then use SSMS...

Data pages make up a clustering key. No data page exists outside a clustering key. if any data in a table with a clustering key is updated then...

I might be misinterpreting what you're saying above but,...

Paul is certainly a worthwhile authority.   I will study his article later.   I did notice this quote, which was emphasized:

A clustered table will always produce full...

Paul is certainly a worthwhile authority.   I will study his article later.   I did notice this quote, which was emphasized:

A clustered table will always produce full logging and...

The data still has to be read -- how else would SQL know that the proposed new value was the same as the value in the...

OK, found one of the links:

https://www.sql.kiwi/2010/08/the-impact-of-non-updating-updates.html

I assume Paul White is an authoritative enough source for you :wink:.

I mentioned another source in my ref notes but can't find it.  My internal...

The data still has to be read -- how else would SQL know that the proposed new value was the same as the value in the table itself?

It's the writes/dirty...

I'll have to check my internal notes for outer references.  My notes just have the relevant details for me, not where I got them from.

But I'm rather busy now, so...

The code below is showing the the exact same cpu times and statistics whether or not the target value is being changed.    Not calling you a liar,...

I agree.  In particular, I would never do this for "ANY" db.  And definitely not in production.  Prod data, particularly, should always be as tightly restricted as possible.