Viewing 15 posts - 5,236 through 5,250 (of 59,072 total)
I'[m always curious... what is the data in the VARCHAR(MAX) column that is being split? Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 11:27 pm
One easy way to find out if autostats is the culprit is to... temporarily turn it off. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 9:00 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 8:55 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 7:21 pm
Awesome! Thanks for the update!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 7:12 pm
Heh... I absolutely love it, Sergiy. +1 billion!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 12:18 pm
I am not sure why you marked the previous answer as spam ...
It may be that no one marked the post as SPAM. It may have been the automatic...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 18, 2021 at 6:37 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2021 at 12:58 pm
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.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2021 at 12:48 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2021 at 12:25 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2021 at 3:26 am
Select b.* from #Imports
CROSS APPLY dbo.UDF_datasummary(a.HS_code) bmissing alias - "a"
Select b.* from #Imports
CROSS APPLY dbo.UDF_datasummary(a.HS_code) b
missing alias -...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2021 at 2:31 am
Resolved
Resolved
So, what was the problem?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2021 at 6:26 pm
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"...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2021 at 6:25 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2021 at 11:09 pm
Viewing 15 posts - 5,236 through 5,250 (of 59,072 total)