Viewing 15 posts - 4,486 through 4,500 (of 59,087 total)
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
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 ERRORFILE and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2021 at 4:11 pm
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.
[Edit] My...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2021 at 4:06 pm
If you filter on step_id = 0, you'll get the info for the entire job instead of the final step.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2021 at 2:26 pm
Have you thought about how many rows are in the table to begin with? If 35m and you're deleting 30m, maybe a faster approach, to
begin with, is to insert...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2021 at 2:14 pm
If you're calling a scalar function, it's RBAR.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2021 at 1:03 am
And yet, I've not seen where that actually matters. And, it won't matter unless you're doing RBAR updates of the same row more than once every 3.3 milliseconds because the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2021 at 4:02 am
If it's a connection pool, then you'll know the benefit... faster connections for your users.
If it's a connection leak, you'll eventually run out of connections.
The disadvantage is that each connection...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2021 at 2:26 pm
Viewing 15 posts - 4,486 through 4,500 (of 59,087 total)