Viewing 15 posts - 1,651 through 1,665 (of 59,091 total)
Welcome aboard, Glenn!
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 11:23 pm
I've seen issues repeatedly with "SELECT ... INTO <new_table>" causing blocking (on SQL 2016). When we adjust the code to split the table creation and...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 10:17 pm
I've seen issues repeatedly with "SELECT ... INTO <new_table>" causing blocking (on SQL 2016). When we adjust the code to split the table creation and the table...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 8:48 pm
I've seen issues repeatedly with "SELECT ... INTO <new_table>" causing blocking (on SQL 2016). When we adjust the code to split the table creation and the table load the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 8:32 pm
Just in case anyone else is reading this and doesn't know, Lynn is anything but a "Ring Knocker". He's a regular on these forums, has written some great articles, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 6:42 pm
I absolutely agree that it may not "be the listener" at fault... especially after seeing so many different "speakers". I definitely believe we're on the same page in that area.
On...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 5:52 pm
Jeff Moden perhaps that is the reason why Option A is sometimes faster and why Option B is sometimes faster my knowledge of DBA aspects is not as deep...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 5:33 pm
Ok... I just did some extensive testing using Brent's code both as is and with some mods to give the test table a bit more bulk.
Using a MAXDOP of 1,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 4:51 pm
It's been my expectation that SQL Server will run slower because of all the stuff they're doing to figure out if a plan should be reverted and a bunch of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 4:46 am
My first motto is (and all my students know it) that the only stupid/dumb/bad question for someone seeking knowledge is the question they chose not to ask.
My motto is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 4:38 am
I know you get some reduced performance from running on a virtual machine by I thought this would be maybe 20% slower, the creation of the clustered index...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 4:25 am
Okay to comment on the (A) CREATE TABLE with INDEX then INSERT INTO versus the (B) SELECT INTO then create INDEX there is no set solution for which is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 4:16 am
You don't really need to partition the table if you (1) cluster the table by date first and (2) the lookup queries specify a WHERE clause on a date...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 3:58 am
@bob-2... you made the comment in your first posts of...
What should be checked apart from blocking?
Did you check for blocking? If so, is there blocking associated with this issue?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 3:50 am
Also another means of getting around all those WITH (NOLOCKS) is to set at the top of the stored procedure either:
SET TRANSACTION ISOLATION LEVEL SNAPSHOT
-- OR --
SET TRANSACTION ISOLATION...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 3:49 am
Viewing 15 posts - 1,651 through 1,665 (of 59,091 total)