I think you missed the suggestion about reverting to the old Cardinality Estimator, which DID fix the same problems we were having when we made the same...

The text file was UTF-8 and we used CODEPAGE = 65001 and were able to process successfully.

set @Str1 = 'Select * Into ##TempPerson FROM OPENROWSET (BULK '''

set @Str2 =...

+1 Billion to Roger Plowman for his post above.  I'll also add that commenting code when you're writing it is pretty simple.  The first thing I normally do is to...

Play with the idea of having a calendar table and then doing a set-oriented EXCEPT operator to find the missing dates and insert a row with the dummy values...

p.s. Even in SQL Server 2016, there's still a limit of the In Memory stuff of 250GB.  In the databases of today, that means you have to be a wee...

I didn't mean that as a slam.  It's just not possible to post general guidlines because everyone's stuff is different.  I just watched the following YouTube on the subject... every...

Yep... let's go back to square one... if they were to move to Teradata and do the same types of things that they've done with their SQL Server, they'd still...

Sorry... you're not going to like this.  My general guideline for things as important as Memory Optimized data is to Google for the documentation and read about it because I...

Great.  I wish you well on your endeavor.

As a bit of a sidebar, consider documenting the various things you did and writing an article about it here on SSC even...

You're welcome and thank you for the feedback.  The question now is... do you know how it works?  I ask because you're the one that is going to have to...

Understood.  A large part of the problem may actually be the 80% Fill Factor thing you folks have done.  It actually takes 25% (not just 20%) more space to store...

OK... here we go... code looks almost the same as before but added a couple of tweaks to do it just for the first of the month... I also fix...

Crud... I have a bug in the code I just posted here... it missed 12/1/2019 and so I've removed the code... I'll be back soon.

That's for equalities.  If you have an inequality, you'll need to reverse the comparison operator if you reverse the order of the columns.

Since you didn't use a variable on the left side of the "=", you've changed it to a column assignment.  Since the variable had no assigned value, it went ripping...