Dave Watts wrote: > In some limited cases, you just might not care that you're getting the > correct data. For example, let's say you're trying to figure out the average
yeah, we use that kind of hinting when we project tax revenues in our municipal applications. big, complex sql is involved against several monster thumping tables and if we miss a few baht (thai currency) here & there, "so what". but i'd suggest there are a few more general cases where it's also applicable, say data used in infrequently used form pulldowns that we know won't be changed where we don't want to waste an app scope or cached query on. if you keep your wits about you, NOLOCK hinting's not a "bad thing". ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225302 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
