the "where" part of the update statment

Hallo,
i noticed in the sql profiler that the ADO dataset produces an update
statment with many "AND" like:

update table set field=value
where primary key=value and this and that and the other and so on.

i understand this is used in a lock optimistick scenario in order to catch
possible changes that may have happned from other users, on the same row i
had modified.
But what if i dont want to use this locking mechanism and instead use mine?
How can i still use batch optimistic mode and at the same time instruct the
ado dataset to use only the primary key column in the update statement?
This has tramendous diference in perfomance in large tables.
We cannot index every column of course.
Any help?

Thanks very much,
Fotis.


.

Relevant Pages

  • Re: the "where" part of the update statment
    ... i noticed in the sql profiler that the ADO dataset ... instruct the ado dataset to use only the primary key column in the ... Please reply to the newsgroup. ...
    (microsoft.public.data.ado)
  • Re: the "where" part of the update statment
    ... i noticed in the sql profiler that the ADO dataset ... instruct the ado dataset to use only the primary key column in the ... Please reply to the newsgroup. ...
    (microsoft.public.data.ado)
Loading