I understand the concept but not how it applies to the situation I'm working with. Suppose today I create a new target table with the VersionCol field you explained...

Have a look at this link for a far better example than mine!

It's not the same, see the following example:

DROP TABLE IF EXISTS #Source;

CREATE TABLE #Source
(
    CrapId INT PRIMARY KEY CLUSTERED
   ,VersionCol ROWVERSION NOT...

• This reply was modified 6 years, 7 months ago by Phil Parkin.

Please do not cross-post. Answers here, please.

Phil - From what I'm reading about RowVersion, that could be a potential solution going forward but won't help looking back at all of the archived tables to determine...

When thinking about it a little differently I have another question. Suppose a daily file with the same structure (300 columns, 3 million rows, and no last modified date...

Are you using an OLEDBCommand task to do this? These are notoriously slow, because they process one row at a time, and I recommend that you re-engineer this as follows:

...

Is there any possibility that you could add a RowVersion column to your source table?

This, in combination with your PK, should allow you to identify rows which contain one...

...

all of our guys have the redgate tools, if you write a "Select * into", hover over it, then it will allow you to generate a CREATE #Table script...

Are there any functions, views or stored procedures in the DB?

If these were written by someone who knows the schema, you may be able to glean some ideas about the...

I hate "where 1=0" - I ..use  "where @debugmode=1" and pass that in as a parameter. the number of times one of my devs has hardcoded "where 1=2"...

Could you use two copies of each table and use synonyms to switch to and fro' every day?

The users query the data using the synonyms & have no need to...

• This reply was modified 6 years, 7 months ago by Phil Parkin.

Shifting gears for a minute... does anyone have experience with BitBucket (source control) and Jira?  Rumor has it that they integrate seamlessly but have zero experience with either so...

• This reply was modified 6 years, 7 months ago by Phil Parkin. Reason: Fix typo

Your OrderRules table should be normalised.

OrderRulesId, AccountId, AllowedState

(One row per allowed state, per account.)

(State could, and probably should, also be normalised.)

With this in place, everything becomes much easier.

• This reply was modified 6 years, 7 months ago by Phil Parkin.

I don't think so.

Can you describe the reasons you think that this would be helpful to you?