sql and nolock -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: sql and nolock
From: Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
Date: Fri, 22 Nov 2019 11:53:49 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Why is it customary that DB2 sql queries generally don't use nolock or "for
read only"? or do they?
Is it mostly only used in much higher availability shops than I am used to?

anyone want to provide insight on this topic?

tia

Jay

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: sql and nolock , dlclark

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.