Quote:
The destination SQL Server column is varchar and I would prefer not to have to change it in this release.
That's a big mistake. It's simple to get the data from excel into the field, but once it's there, it's there until you need to use it - and at that point you will start to get problems. NVARCHAR fields should only be used for text data - mobile numbers, names, addresses, product descriptions: anything you aren't going to try to compare numerically or sort by anything other than a basic string comparison.
And that includes dates. In a string based sort, the comparison is wholly based on the first pair of different characters in the two strings, everything else is ignored.
so "2/3/2022" is before "4/3/1955" but after "1/3/2100".
And converting this when you need to use it is a nightmare as someone. somewhere, somewhen will put "today" or "I dunno" in there instead and your code will fail.
Bite the bullet, change your datatype to DATE, DATETIME, or DATETIME2 and the "month first" / "day first" problem becomes just a matter of preference in the presentation software, instead of a nightmare that will haunt you for years to come.