Would you please provide directly usable data, i.e. CREATE TABLE and INSERT statement(s) for the sample data.  [A splat of data on the screen does us no good to try...

Congrats, very nice article.  Informative and to the point.  And it's so great to see an intersection ("bridge") table without an identity column, instead keyed by the parent's keys, the...

There was very likely different activity on the two servers.  That could cause SQL's missing index recommendations to change, which would in turn likely cause BlitzIndex's recommendations to change.  (Note:...

I think there was a bit of a typo there, CR + LF is (13)+(10), not (10)+(13).  You probably also want to replace single CHAR(10)/CHAR(13) chars, to be safe, like...

No, on a non-partitioned table, there is no way to build chunks / parts of indexes (frankly I think there should be, but there isn't).

Typically people use a NULLIF like below, to avoid a CASE statement -- whether you prefer that or not is, of course, up to you:

ISNULL(((JobInfo.EstHrs / NULLIF(JobHrs.ActualHrs, 0)) * 100),...

If the NULL determination was not a 1-time thing, but needed to be periodically available, I'd use triggers to maintain a counter per column in another table that "told" me...

That's what I assumed it meant. Other interpretations didn't make sense. I suppose writing the table name and column name to at least a temporary table and then...

I'm not sure specifically what the OP meant by "records [presumably meaning rows] for only the columns that have data in them".

Does that mean rows with NO null columns at...

Nice.  Don't feel bad, we have views that do this:

SELECT ...

FROM OPENQUERY(remoteserver1, '...')

UNION ALL

SELECT...

FROM OPENQUERY(removeserver2, '...')

UNION ALL

SELECT ...

FROM dbo.local_table

No way to match up all the sources to the destination for...

Does the function use schema binding?

Please provide the text of the function, naturally first obscuring any names you need to protect.

I don't see any way to do this.  A view could have columns from several different referenced entities and from no referenced entity at all (such as CREATE VIEW dbo.view_name...

SQL has an easy built-in way.  When the analysts are given SELECT permission, the DBA can add the "WITH GRANT OPTION" to their permissions.  That gives them permissions to grant...

No, that should do it, it must be something else.

Can you copy out the statements around where the error occurs and parse those directly and see if you can spot...

Or maybe you need this?!:

...

AND SOURCE_ID <> 100 AND ADDRESS <> 'NOT APPLICABLE'