By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,070 Members | 1,237 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,070 IT Pros & Developers. It's quick & easy.

db2_evaluncommitted , db2_skipinserted and db2_skipdeleted

P: n/a
Hi

I was wandering if someone has seen a bad side of using one of these
parameters ?
Amy performance problem ?

Since with db2_evaluncommitted, db2 evaluates the where clause before
locking, I was thinking that may cause a performance degradation.

thanks
Stephane
Jan 9 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
stepaq wrote:
Hi

I was wandering if someone has seen a bad side of using one of these
parameters ?
Amy performance problem ?

Since with db2_evaluncommitted, db2 evaluates the where clause before
locking, I was thinking that may cause a performance degradation.
Stephane the WHERE clause has to be evaluated one way or another.
Note that this only applies to predicates in the WHERE clause that can
be pushed down that far (aka. Sargable or Type 2 predicates).

I have a hard time imagining a performance downside for any of those.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Jan 10 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.