If you're using 500GB now, it could be very hard to squeeze down to 128GB.

It's likely, however, that you are not using data compression now.  From SQL 2016...

Please don't state that "COUNT" and "TIME" are reserved words in SQL Server because they are not.

In fact, you cannot restore any newer-version SQL Server db to any older-version SQL instance, period.  Just does not work.

If you're using 500GB now, it could be very hard to squeeze down to 128GB.

It's likely, however, that you are not using data compression now.  From SQL 2016 on, that...

EXEC msdb.dbo.sp_update_job @job_name='<your_job_name>', @enabled = 0 /* to disable, or 1 to enable */

You're not going to be able to this calculation:

ISRECNUM % 20 = 5

sargable.  By definition, it just isn't.

Actually, the development team should have nothing to do with how the data in the db is physically stored.  That's the DBA's job.  (Sorry, just...

Absolutely correct.  McAfee could end up damaging your db files, esp. log files.

I suggest using a table to simplify the calcs:

;WITH test_data AS (
    SELECT CAST('08/31/2021' AS date) AS [Period date], CAST('07/31/2022' AS date) AS [target...

Actually, the development team should have nothing to do with how the data in the db is physically stored.  That's the DBA's job.  (Sorry, just had to...

I suggest using SUM rather than COUNT.  THEN 1 ELSE 0 is a consistent, clean pattern, whereas THEN 1 ELSE NULL is a kludge.

,SUM(CASE WHEN tc.IsEnabled =...

Could you post directly usable data -- CREATE TABLE and INSERT statement(s) -- rather than just a picture?  We can't write SQL against a picture :-).

You don't need to use variables.  I also suggest sticking to the "best practice" technique for getting a specific date value.

An index would be best on ( asis, twdatum );...

Actually, the development team should have nothing to do with how the data in the db is physically stored.  That's the DBA's job.  (Sorry, just had to say that first.)

I'll...

If you don't need to worry about possible blank chars in the data, you can remove the trimming.  I did it just as a safeguard.

;WITH test_data AS...