So how do you know this will be run "thousands of times a day"?  I wouldn't expect it to called anywhere even close to that many times.

I did not add...

Which version of SQL Server?  If you're in a recent enough version, you can use function TRY_CAST to see if the value is a valid int or not.

exec sp_executesql @sql = @sql, N'@date datetime', @date

Are you sure you need a specific datetime and not a range value such as the current day?

Actually you could be causing a performance problem by getting SQL to use the same query plan for different values, i.e., by avoiding the "overhead" of...

As to licensing issues, talk to an expert on that.  Licensing has gotten really complex, you need someone who truly studies to know all the details on that correctly.

Actually you could be causing a performance problem by getting SQL to use the same query plan for different values, i.e., by avoiding the "overhead" of a recompile. ...

You can use CPU affinity to reduce the number of CPUs available to SQL Server.

196 cores?  Wowza that's a *lot*.  If you're only at 25% usage, you presumably would be...

Actually you could be causing a performance problem by getting SQL to use the same query plan for different values, i.e., by avoiding the "overhead" of a recompile.  The first...

Below is some code that will probably do what you want.  I strongly recommend you run it first with the EXEC() commented out.  If all of the output looks ok,...

If I understand correctly, you just need to add the condition on the JOIN:

...previous_part_of_query_same_as_before...

INNER JOIN #temp_Lookback t2 ON t1.Id = t2.PreviouslyCompletedId AND t2.Type = 'F'

You'd typically want to use dynamic SQL for this, so that only the relevant columns were included in the comparisons.  You'll also typically want to recompile to get a specific...

It definitely could, esp. if there's an index containing the type column.

First try refreshing the view.  The "*" in the view may be causing some issues if the table has changed after the view was created.

I have to disagree.  If you use...

I'd say it depends on how often you need to show the resolution duration.  That's a rather complex calc to do repeatedly.   And presumably the Resolution Time would only be...