A quick example:

DECLARE @Who TABLE
(
    SPID CHAR(5)
   ,Status NVARCHAR(50)
   ,Login NVARCHAR(50)
 ...

Can you use a table variable?

I think you'll need recursion to solve this. Try running the following:

DROP TABLE IF EXISTS #table2;

CREATE TABLE #table2
(
    id INT NOT NULL --PRIMARY KEY...

NOT LIKE '836%'

works. If you think it doesn't, please provide a query which we can run to prove otherwise.

Note also that SSISDB does not contain any jobs, merely packages, logs, environments and configurations.

Do you have the Master Key from the original server? That is, the key used to encrypt (some of) the data inside SSISDB?

Or maybe this?

a) Users are querying table set A via synonyms

b) ETL process loads table set B with data from file1

c) ETL process switches synonyms to point to table set...

Great Idea! Thanks Phil. This would work if they were loading a full set of data each day, but unfortunately its an incremental load, meaning 24 hr of data...

I know of no other way.

This will run like a slug (because no indexes can be used), but try

...
WHERE
CAST(RecvdDate AS Date)...

Any reason for not changing [RecvdDate] to a Date?

Here is what I found. db2 - account_no - data type - decimal sql - account_no - data type - decimal in lookup, i have to use both columns...

Don't remember reading about that in BOL!

I called it a daily file in my hypothetical scenario of one that has the same structure of the tables. Sorry if that was not clear or got lost...

Did you do your research into the new cardinality estimator? See here, for example.