Actually, you did...

Actually, the development team should have nothing...

You were attacking a straw man.  I never made anything close to the claim you said I did./quote]

Actually, you did...

Actually, the development team should have nothing to do...

Those would work although those particular dates are a wee bit into the future assuming those are the little-endian count of days since the first of January 1900.  One of...

an aside: Azure Synapse cannot do recursive CTEs (or heirarchyid...), if you happen to be working in that realm.

I settled for a few layers of nested CTEs down to...

The "base date" for SQL Server for temporal datatypes is 01 Jan 1900 and it has a "Date Serial#" of "0".  All other dates are based on the number of...

A calendar table is great for that. But if you want to derive it dynamically, and you're always executing on the day following the end of the date range:

What would be interesting is to see if the stored procedure actually uses the end date correctly or if you going to miss all but the firs 3.3 milliseconds of...

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...

I am trying to get the lowest cost for a part and the highest cost for a part. along with the dates that they occurred. I almost have what...

Lordy... It would have been RIEALLY nice if you left the original question here so that others no what the final recommendation was about.

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...

No. The CU will update all of the features you have installed.   You can un-select features to update in the install of the CU, but you probably would not...

I fully agree with the comments made by others, but if the OP would like to try anyway, this will work with the test data provided:

...

Even if you have a prior agreement - and the provider is sending the data in YYYY-MM-DD format you could still have problems depending on the data type and...

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...