Viewing 15 posts - 136 through 150 (of 2,620 total)
SELECT *
FROM TableA A
WHERE NOT EXISTS(SELECT *
...
March 20, 2024 at 7:12 pm
DROP TABLE IF EXISTS MemberDiagnosis;
go
-- Create the table
CREATE TABLE MemberDiagnosis (
MemberNbr INT,
dx VARCHAR(50),
dx2 VARCHAR(50),
...
March 20, 2024 at 2:36 pm
" If Table Scan (heap) does that exactly that, then what is the problem to use the index, which will actually be able to help finding those records quicker? Or...
March 20, 2024 at 9:26 am
Is there an explicit BEGIN TRANSACTION in the code with no COMMIT?
March 19, 2024 at 12:11 pm
MY_ADV.Pub.value('(reference_number)[1]','varchar(10)')
March 19, 2024 at 12:03 pm
We collect these statistics on a weekly basis. This way we persist runtime history for all monitored instances.
This comes in handy when provisioning for growth or planning migrations.
Devs and...
March 18, 2024 at 7:51 pm
If you don't have all the columns that are included in the query in the index then SQL Server will have to read the index then go off to the...
March 18, 2024 at 10:02 am
Apart from saving space it is unlikely that rebuilding or reorganising the index will improve the performance of anything, in fact it might make it worse.
It sounds like the entire...
March 16, 2024 at 5:37 pm
I am surprised that no one else answered the original question - and this just evolved into using temp tables and trying to solve the performance issue using a...
March 16, 2024 at 4:10 pm
duplicate
March 15, 2024 at 11:20 pm
I see many people that site things like a lack of training at work, etc, etc.
Tell me... if you have a degree, who paid for it? How did you...
March 15, 2024 at 11:15 pm
One more thing...
The create table and create index code was created before any rows were added to the temp tables. Not sure why the run time grew like that. ...
March 15, 2024 at 6:50 pm
Hello,
I have found the problem, in my indexes i forgot XKRES table I missed that there is difference: XHRES and XKRES.
After preparing the indexes now uses all...
March 15, 2024 at 1:43 pm
I am getting an error
Msg 468, Level 16, State 9, Procedure dbo.WIP_Query_V2, Line 462 [Batch Start Line 2]
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS"...
March 15, 2024 at 5:27 am
You need to remove the drop existing bit, as there is no existing index on a new table.
March 15, 2024 at 4:39 am
Viewing 15 posts - 136 through 150 (of 2,620 total)