testing this the first statement updates 2 rows, the second statement again all rows because m.ID is not a row of the subquery and so does not limit the updates...

• This reply was modified 6 months ago by  joerg.kannengiesser.

@steve-2: with your statement same problem, because ts.PKey is not column of subquery.

Must be: Q1.myKey

update ts
set ts.WertA = 'TEST' 
from TempSel ts
where ts.PKey in (select...

in th example of course I coul do it like

UPDATE TempSel SET WertA = 'TEST' WHERE PKey LIKE '3%';

the selection for the records to update was much...

your are right: using a qualifier results in an error (unknown column):

update TempSel set WertA = 'TEST' where PKey in 
(select Q1.PKey from (select PKey as myKey...

Thanks a lot for your help and quick response !

hm .. but why does the optimizer not solve this ?

Is it to me, to control and change the select-Statements ?

I took a closer look to the execution plans: can't see big differences ... the main Job is the "RID Lookup" with about 70% but very small costs in both...

script attached ...

some indexes on objkeys are stupid for searching (e.g. okeydata without okeyname / okeyno) but were released by the software vendor;

we added the "KH_..." Indexes for better Performance...

objkeys has several columns ... we need parentid (key to the object-table), okeyname and okeydata

(okeyname is the Name of the value and okeydata is the value itself,

e.g. okeyname "VENDOR"...

Server-language is set to: "Deutsch (Deutschland)" / "German (Germany)"

Language in Connection-Property for both database is: "Deutsch (Deutschland)" / "German (Germany)"

sure .. so break it down:

where can I set the datetime-format for a specific database or database / user / field ?

It seems, that MS changed something in the optimization,

maybe it's a bug in 2005R1 - I will check this again after installation of SP3.

Does anyone know if there's a detailed...

Of course it doesn't appear if there is a full-covered-index.

The problem was broken down, so the DMS-software joins this

table with other tables where some columns can't be included into the...

sql-plans attached.

the story is going on:

after inactivating the pw_index in the 2005R1,

the SELECT with "=" uses the still remaining index (with "included columns"),

after deleting the pw_index in the 2005R1,

the SELECT...

sql-plans in attachment ...

How can I delete this post ... ?