Need sample data that is directly usable, that is, CREATE TABLE and INSERT statement(s), not just a splat on the screen.

D'OH, sorry, that should be:

CAST(GETDATE() AS date)

You've already got restrictions based on @LOOK_BACK_PERIOD in the WHEREs, it would just be more efficient to pre-filter rather than waiting until some processing has been done on all the...

Did you add the WHERE condition for the TXN_DATE?  If you have a long history in the table, that would help the most.

Then try an index on (txn_date, company) include...

Need the DDL for the table to sure of more specific recommendations for best speed, but, assuming you will keep a long history in this table:

(1) Either: (A)...

Need the DDL for the table to sure of more specific recommendations for best speed, but, assuming you will keep a long history in this table:

(1) Either:

(A) cluster the table...

I've done similar set ups.  Dynamic SQL is definitely a good choice here.  To keep the FilterAttribute column consistent, I suggest you use a different column to control include or...

The *data* file drives should be 64K.  Log file drives should still be 4K.  If you mix data and log files on the same drive, you'll want to use 64K.

SELECT T3.SYMBOL,
T3.TRADE_DATE,
(AB30_C + AB30_P + AB30_G + AB30_R + AB30_Y) / NULLIF(SUM(CASE WHEN AB30_C = 0 THEN 0 ELSE 1 END + CASE WHEN AB30_P = 0...

I would think you would want four ids:

drive full path (other than drive, of course) filename extension

When new data comes in, you'd pre-add any new ids before loading the...

I would think you would want four ids:

drive

full path (other than drive, of course)

filename

extension

When new data comes in, you'd pre-add any new ids before loading the main table.  That way...

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,
...