You shouldn't be validating password in the SQL in the first place. The fact that you are means you are passing the password as Rae text to the SQL Server...

You have 2 options really. Use CHECKSUMand run the risk, or upgrade to SQL Server 2016+.

Ok, the problem is HASHBYTES. The maximum length, on SQL Server 2014, is 8000 characters. You can't use a varchar(MAX) with HASHBYTES on SQl Server 2014-.

So why are you using SET ANSI_WARNINGS OFF when there is no truncation? Notice Jeroen has said the same thing in SO that I said here; fix the truncation issue....

Why not fix the truncation problem instead? That would seem the better idea.

(Also, duplicate thread on Stack Overflow: https://stackoverflow.com/questions/52891568/set-options-issue-on-sql-server-2014 )

Rather than using a JOIN with the clause InActive.RowNumber = Active.RowNumber -1 you would be much better looking at the LEAD and LAG functions....

Why not use a PERSISTED Computed Column? In a very simple sense:

Triggers? Contraints? Impossible for us to tell without the SQL and DDL of the objects involved.

In fact, I said "a couple" of years earlier, but it's actually less that that. SQL Server 2008 is out of extended support in September of next year, which is...

SSMS 2017 (and 2019 preview) support all supported version of SQL Server, which (for now, but not for much longer) includes SQL Server 2008.

What about if a row is updated or deleted? Do those need to go across too?

Still, SSIS is unlikely to be the roght tool here; especially if...