Somewhat confusing, the right join looks odd, but, anyway, you might try this and see if it produces the result you need:

;WITH DUniques AS (
  ...

You've got some choices, some more annoying than others:

(1) Use an INSERT trigger to check for dups and cancel if a dup would be created.

(2) Create additional columns that are...

That's somewhat confusing.  Do you want to not allow mixed case at all?  Or do you just want to prevent a duplicate from being inserted, basically ignoring case in determining...

;WITH Cte_Persons AS (
    SELECT *, ROW_NUMBER() OVER(PARTITION BY Name ORDER BY Id) AS Row_Num
    FROM @TBLPERSON
)
SELECT
    Name,
...

You can't use declared RI, but you could write your own.

As to the design, I assume the EntityIDs of the various tables -- Person, Service, Organisation, etc. -- overlap.  That's...

I think my code would adjust as follows to check program_date for inclusion:

SELECT ca1.*
FROM dbo.cust_sales_temp cst
CROSS APPLY ...
FROM (
    SELECT month#, sales, ROW_NUMBER() OVER(ORDER...

SELECT ca1.*
FROM dbo.cust_sales_temp cst
CROSS APPLY (
    SELECT cst.customer_id, cst.program_date, 
        MAX(CASE WHEN row_num = 1 THEN sales...

Recursion is notoriously slow for iteration.  Maybe use a "standard" tally table instead:

;WITH
cte_tally10 AS (
    SELECT * FROM (VALUES(0),(0),(0),(0),(0),(0),(0),(0),(0),(0)) AS numbers(number)
),
cte_tally100 AS (
 ...

CREATE VIEW must be in a batch by itself, i.e., without GOs, you could create only one view per script.

Since GOs are likely not valid, that may be what you...

In this case it doesn't.  But what is the harm in CASTing?

The first three rows in the table DO all match the first "<" condition: 00:05:xx and 00:10:xx are less than 00:15:xx.  Only the second condition limits the result to a...

For example, when the lengths are consistent, it seems to produce the desired result:

DROP TABLE IF EXISTS #xr;
CREATE TABLE #xr ( length_min varchar(8) NOT NULL, length_max varchar(8)...

It seems like this is a character comparison.  If so, "00:15:18" would not compare correct "0:...", since you have two leading zeros vs one leading zero.  If you're going to...

Don't change the CASTing for the bits in the WHERE clause, leave as is.  Otherwise I believe SQL will default to a different data type which would force a column...

I generated SQL separately for each view, even though that requires a cursor.  In this specific case, I think you may want to be able to control things table by...