Viewing 15 posts - 5,371 through 5,385 (of 59,089 total)
Ken McKelvey wrote:You might be interested in an interesting series of articles by Itzik Ben-Gan:
https://sqlperformance.com/2021/04/t-sql-queries/number-series-solutions-4
Ken, Thank you for posting this link.
I was involved in that series for...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2021 at 2:28 pm
Note that Microsoft is preparing to switch, yet again, to a different feedback system.
Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2021 at 2:03 pm
I use this function with recursion and @top of 1000000 is enough for me, but I don't n know if it performs better:
-- by Carlo.Romagnano CREATE FUNCTION dbo.fn_tally(@top...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2021 at 1:44 pm
Personally, I like the 5th option, which wasn't included... Run the two versions of the same query in the same window and compare the execution plans that show.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2021 at 2:40 am
I know this is an old post but I just ran across it again while looking for something else. Probably doesn't make any difference to anyone anymore but...
Going through it...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2021 at 11:11 pm
Heh... I agree with Grant on logical execution being left to right and data flow being right to left and both being top to bottom (except on super-umbra-red moons on...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2021 at 2:34 pm
Yep. Without the rest of the error message, I can't even hazard a guess. Jeff is probably right (says Grant all the time).
Thanks, Grant. I'm humbled but I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2021 at 2:21 pm
Don't you have access to the rest of the failure message from the SQL Server Error Log?
If I had to guess from the truncated message above, I'd say you may...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2021 at 1:14 am
what about fn_dblog?
I updated a table with the same value and after doing this there were two more rows returned by fn_dblog. each time I ran the (duplicate)...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2021 at 9:39 pm
You can actually setup an alert for blocking and then you can have that alert call a stored procedure to get some amplifying information, record that information...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2021 at 9:17 pm
Heh... it's not my story. It's in the link you provided. Paul proved it with code. Can you prove it to be otherwise with code?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2021 at 6:54 pm
Not looking for a solution just some suggestions for methods that have worked well for others.
You can actually setup an alert for blocking and then you can have that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2021 at 5:34 pm
Personally, I'd check the SQL Server Error Logs for deadlock events.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 19, 2021 at 6:04 pm
Wow. I've never actually heard of any third party (nor anyone else, for that matter) using auto-close on a database before. Thanks for taking the time to post what you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 19, 2021 at 12:08 pm
I've been pretty happy... as some say... "Loving the lockdown". But, I have to agree with you Grant. Being around people does promote spontaneous discussion, which supports and enables the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 19, 2021 at 12:04 pm
Viewing 15 posts - 5,371 through 5,385 (of 59,089 total)