lots of things can cause that - but without table definitions (including indexes and FK's), row counts for each table, view definition as well as any function used within those...

LastName INCLUDE (ProductID, FirstName) and LastName INCLUDE (FirstName) are the same in this case as ProductID is the clustered index "key".

regarding your indexes I misread your original post.

LastName, DateDeleted INCLUDE(FirstName)WHERE...

was apply available on sql 2005?

your issue is not the ProductID but the DateDeleted. This last field is what is causing the key lookups as it is not part of the second index (ProductID is...

might be worth checking filenames of attachments - could also happen that someone adds a filename with special characters just in case it does not go through same code

try and change the keywords to match the EXACT casing for install as per documentation.

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt?view=sql-server-ver15

there were other users reporting errors where this sorted the issues they had.

setup.exe /UpdateSource="E:\SQL_2019\patches" /ACTION=Patch /AllInstances...

its more than that - and it can be done with set based instead of a cursor assuming doing it in T-SQL alone.

but take in consideration this aspect you have...

because your node names is not reports/report but RECORDS/RECORD

cross apply c.nodes('/RECORDS/RECORD') as A(REPORT)

thats fine -

what I have, which is what I told you to get, is a I7, 6 core, 32GB ram , ssd disks.

I do heavy processing on it (db is...

and be careful with inserting data onto remote server through a linked server . it is EXTREMELLY slow as it does it a record at the time.

if there is any...

if you already have a good spec (you didn't tell us what you have) then you might be better off supplying us with some of your "bad behaved" queries and...

sorry but I did not say that is should be 10-20% max.

What I said is that in one of my servers (and we have over 800 SQL servers) we have...

get an I7/I9 with 6 cores+ and 32GB+ ram and some SSD disks.

you may also need to tweek max DOP and CTFP so your queries to not overload the machine....

• This reply was modified 4 years, 10 months ago by frederico_fonseca.

what may have left you bad was mixing cpu with log file growth.

although for SQL to grow a file it requires a small amount of cpu that is not enough...

can you supply a ACTUAL plan instead of estimated of a query with problems - a 1 row estimated is not an issue

on the plan you supplied your big issues...