Viewing 15 posts - 1,666 through 1,680 (of 59,099 total)
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
Note I teach/tutor for free and have an online Discord server with 80 plus students at verying levels of expertise. My first motto is (and all my students know...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2023 at 2:59 am
Indexes are needed as the temp tables are joined to other tables, without indexes the queries would take a lot longer.
You and I have know each other for a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2023 at 8:14 pm
Perhaps a better thing to do is to partition the table?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2023 at 7:53 pm
Post deleted... I misread what was being done.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2023 at 7:51 pm
Scott's synonym suggestion sounds like your best bet to me.
Strong second here on Scott's synonym suggestion.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2023 at 7:47 pm
Thanks, Steve.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2023 at 7:44 pm
Just to ask the question, have you checked the datatype for those columns in the base table?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2023 at 7:42 pm
Viewing 15 posts - 1,666 through 1,680 (of 59,099 total)