One easy way to find out if autostats is the culprit is to... temporarily turn it off. 😉

Having a quick look at what you attached, here's what I would do...

I'd lay out a staging table with the correct columns with the correct datatypes.

I'd then setup to do...

There are actually a couple of compounding problems with the code... and it's not because of the code... it's because of the stupid stuff MS has done.

First, there's a problem...

Awesome!  Thanks for the update!

Heh... I absolutely love it, Sergiy.  +1 billion!

It may be that no one marked the post as SPAM.  It may have been the automatic...

Thank you Jeff,

The target table is to be used for only one processing and won't be used by any other users at all. it's like a collection bucket.

That's why...

I'll try to get back to this later today but... the load should not actually cause the Clustered Index to fragment... if I'm reading things right, it's a wholesale load/replacement.

Yep... you can avoid a staging table if you'd like but... if something goes wrong, there's going to be a long rollback and your target table might be close to...

No.  And deleting a mistake that you found on your own would be depriving someone of some information that might help them in the future.  I'm glad you found it...

Select b.* from #Imports
  CROSS APPLY dbo.UDF_datasummary(a.HS_code) b

missing alias -...

So, what was the problem?

It may be that this could mostly be done during the original insert into the staging table.  In order to know that, we'd need to know what the "Facets Feed"...

One of the methods to read a CSV file is to make a "temporary" linked server, use it, then drop it.  I don't know enough about SSIS to say that...

My apologies... I flat out forgot that this is a VENDOR supplied table.  I absolutely agree with the others but will take it one step further... unless you get written...