Viewing 15 posts - 5,746 through 5,760 (of 59,089 total)
Hi all, I have one "heavy" query on my DB. It executes 2400 times per day and I don't know how to optimize it. Do you have any idea?...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2021 at 4:34 pm
Ah... be careful on the Clustered Index recommendation. While such a recommendation can help a lot of things, especially this particular problem, changing the Clustered Index without understanding the impact...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2021 at 4:25 pm
I'm thinking the answer is pretty simple... you probably have more than one WorkOrder per invoice and that made a one-to-many join, which creates more rows (essentially, a duplication of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2021 at 4:13 pm
Heh... I should have put a smiley-face after the "you're wrong" part just to make sure other's knew the kind of relationship you and I enjoy (although they may never...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2021 at 4:01 pm
I've found that what you're referring to as an MVP (Minimum Viable Product) is usually a travesty even when it comes to functionality, never mind security. This is why "DevOps"...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2021 at 2:58 pm
Heh.. and by the same token, blue jeans never seem to go out of fashion. In fact, people have been paying extra for a long time to make their jeans...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 29, 2021 at 8:01 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...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 29, 2021 at 7:14 pm
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
Viewing 15 posts - 5,746 through 5,760 (of 59,089 total)