Viewing 15 posts - 5,731 through 5,745 (of 59,072 total)
Confirmed error in 2016 Enterprise and Developer Editions with latest CU.
Msg 596, Level 21, State 1, Line 0
Cannot continue the execution because the session is in the kill...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 28, 2021 at 8:07 pm
Note: Your example shows double quotes, not parentheses.
FIELDTERMINATOR=‘","’,
My apologies. I corrected the original question to say "double quotes". Not sure why I did...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 28, 2021 at 7:46 pm
Ah... you're correct. No pivots required for this problem so no Cross Tab (although the code is nearly identical... just missing a CASE in each sum for the non-CROSSTAB stuff). ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 28, 2021 at 7:37 pm
The thing above (which you posted) is actually "just" a CROSSTAB (which will have a GROUP BY) with a ROLLUP. With the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 28, 2021 at 7:01 pm
From looking at the results of sp_whoisactive I can see before the CPU got maxed I started to see a high number of RESOURCE_SEMAPHORE_QUERY_COMPILE wait types, these carried on...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2021 at 3:52 pm
I think a good beginner project would be to write a simple checkbook system in T-SQL and then expand on it with thinks like allocation categories in the "memo" of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 22, 2021 at 6:05 pm
It would appear that you have a table full of generic column names and that you're using a different table to define what those column names should be or used...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2021 at 5:26 pm
I am confused whether its my call to decide this change or how & what to inform the management.
Sorry, I missed that part. I would say that it's NOT...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2021 at 5:04 pm
If you stop calling it "Pre-Prod" and start calling it "UAT", there will be no question that it's not actually a production environment. Of course, no part of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2021 at 4:32 pm
If Execution speed is the only issue, can we move ?
There's only one way to know for sure... stand up an instance on your dev box and test it.
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2021 at 4:26 pm
But remember not all is glitters that is new, MS have had a habit recently of breaking servers with patches, probably best to leave it a month or so...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2021 at 4:23 pm
PRINT may also be substantially delayed an may not show up in some job output in SQL Agent. I use RAISERROR('somemessagehere',0,0) WITH NOWAIT; for almost real time feedback (but even...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2021 at 4:01 pm
If you want all of that, you should buy a monitoring product where you don't have to worry about what the code actually does.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2021 at 3:57 pm
It is sometimes a pain but that's my usual tact... if you know something can/is going to go wrong, you need to be ready to pick up the pieces and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2021 at 2:51 pm
Allowing failure: Steve and others use children learning as an analogy for this. That works very well because this is childish. When I am a member of your team,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2021 at 10:04 pm
Viewing 15 posts - 5,731 through 5,745 (of 59,072 total)