select * from table where sportyear=DATEADD(YEAR, -1, @year)

Please be more specific on "Does not work" for Q.ArrangementType.  In general you should have no problem referencing columns in the view in a NOT EXISTS, so some other error...

If you're truly on SQL 2016+, as you said, you can use SESSION_CONTEXT, as below.

It's easier if the tables have the exact same structure, but we could "fudge" around it...

Oops, yep, sorry.  A copy/paste where I accidentally left the ", 0" at the end.

Something along these lines:

Declare @jan01 date
Set @jan01 = Dateadd(Year, Datediff(Year, 0, GETDATE()), 0)

select
Case Left(PeriodID, 3)

When 'Jan' THEN Dateadd(Day, -1, Dateadd(Month, 1, @jan01), 0)

When 'Feb' THEN Dateadd(Day, -1,...

Use just one date for each month; in keeping with "standard" practice, I use the first of the month.

Also, you must remove H.Quantity from the GROUP BY.

select...

Again, MS is following the relational model, where a set does not have a defined order.  That may be fine theoretically, but in the real world we often do need...

Here's another alternative to splitting, to show how CROSS/OUTER APPLY can assign alias names to computed values that can be used in subsequent APPLYs and in the SELECT itself, without...

Presumably MS is following relational theory, where the order of a set doesn't matter.

But, in the real world, the order often does matter a lot, especially when the set has...

Note that you don't have to drop the index and re-create it.

Instead you can DISABLE it, then REBUILD it.

ALTER INDEX no_dups_index ON dbo.your_table DISABLE;

UPDATE your_table

SET ... = ... + 5

/*WHERE...

SELECT MonthCount AS [Total Entries],
    DATENAME(MONTH, RecvdMonth) + ' ' + CAST(YEAR(RecvdMonth) AS varchar(4)) AS MONTH

FROM (

SELECT

DATEADD(MONTH, DATEDIFF(MONTH, 0, RecvdDate), 0) AS RecvdMonth,
COUNT(ID) AS...

You could do this using a stored procedure.  The structure can be returned by the query itself, you don't have to pre-define it.  In theory there are potential SQL injection...

I can see that, so another try with the code again.  If I've done dup posts, admins please delete the extraneous post(s).

I've been extremely busy and so haven't had time...

I can't see my own last post(s), so I don't know if it(they) showed up or not.

I'd urge you not to use a temp table for that.  If SQL goes down during the processing, you'll never be able to determine what the original key values were.