Viewing 15 posts - 4,456 through 4,470 (of 59,069 total)
Getting back to the original post... you do know what sys.dm_db_index_physical_stats() is for, correct?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2021 at 4:34 pm
Dear Jeff Moden, thank you for you kind help! what you said is quite right.
if I ran it on the same server, sometimes it works fine, but sometimes not...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2021 at 4:32 pm
thank you Jeffrey Williams, the table has clustered index, but when I used "alter table oldtable rebuild" , the table released a lot space, many thanks!
when I did this...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2021 at 3:07 pm
Thanks for the reply, Stephen. You should keep track of how things go along the way. This migration would make an awesome article .
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2021 at 2:19 pm
I'm having the same problem time-wise. As the old saying goes, "So say we all". 😀
I also have to admit there's great incentive in learning something new if...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2021 at 2:04 pm
Jim,
Only you can answer a few questions about your article that have been nagging at me because I'd like to do some extra testing by setting up some test data.
You...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2021 at 2:33 am
I've worked on a big personalisation project that produced a distance score between 250,000 products for 5 million customers. That was 1.25 trillion records generating 37TB of scoring data.
The...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2021 at 2:07 am
I'm having the same problem time-wise. As the old saying goes, "So say we all". 😀
I also have to admit there's great incentive in learning something new if you MUST...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2021 at 8:36 pm
My recommendation would be to read the documentation for BULK INSERT, which is located at the following URL:
https://docs.microsoft.com/en-us/sql/t-sql/statements/bulk-insert-transact-sql?view=sql-server-ver15
The two keywords to search for in that article are...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2021 at 8:27 pm
As much as I deplore the use of Cursors and While loops, I have to agree with JediSQL... sometimes there actually is no other way. You probably won't ever see...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2021 at 8:13 pm
Way to go, Grant! I'm still learning new stuff about T-SQL and SQL Server. 🙂
And good article although I do have a couple of black eyes from beating myself up...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2021 at 6:38 am
I'm just curious... what are you going to use Snowflake to determine? Or is this one of those things where they might yet be sure but will do more with...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2021 at 6:25 am
A trigger is the perfect approach for this. Some developers just irrationally avoid triggers no matter what.
Be sure to specify option FIRE_TRIGGERS in your BULK INSERT command.
The...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2021 at 3:42 am
I suggest there's more that could have been covered here, for example:
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2021 at 5:30 pm
Just to add to that, I NEVER bulk insert directly into the final table. I ALWAYS load into a "staging" table and then do validations and dupe checks between that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2021 at 4:16 pm
Viewing 15 posts - 4,456 through 4,470 (of 59,069 total)