Except for the occasional Indexed View, this is one of the many reasons why I hate views.

Instead, try a "parameterized inline view" better known as an "Inline Table Valued...

This will identify rows that don't match:

SELECT [D1].[RowID] AS [D1_RowID],
       [D1].[PairID] AS [D1_PairID],
       [D1].[SequenceInt] AS...

what mention of weekends? there is nothing on the original OP post that mentions it...

Is this solution is only good if there are no dates falling on weekends?

@frederico_fonseca I had the same idea as you initially, but your solution will not work either. What if there were 20 groups instead of 3? What if the gaps...

I think the query can be simplified to this:

SELECT @RowCount = COUNT(*)
  FROM Quality q (NOLOCK)
 WHERE (q.Quality_Date <= DATEADD(DAY, @Interval,GETDATE()) 
    ...

This is probably the fastest code but a bit long winded

declare @Delimiter char(1) = '/'
;with cte as
(
    select 'Invoice/14/248/TD C/O BGIS/20009. 1/ 16566/JB App...

In the UK too

That...

Definitely use char(2) for the values, as suggested (varchar requires two bytes of extra overhead (to store length) per column).

If they're not already encoded, encode the names.  That is,...

I think I would resort to the RBAR cursor method:

DROP TABLE IF EXISTS #Results;
CREATE TABLE #Results(Score int, ActivationTime datetime, Grp int, BaseDate date)

DECLARE @Score int, @ActivationTime datetime
DECLARE...

It would save 2/3rds of the memory required if it could be...

It would save 2/3rds of the memory required if it could be a numeric...

The maximum row size in SQL Server is 8,060 bytes. If you get near this then you might come across performance problems with page splits when updating rows. For this...

It's for a clinical situation. I guess later it can be delivered as a .csv. For now my manager wants to review data and he wants to see it...