Hi, reading the top 10 best practices in Integration Services (http://sqlcat.com/sqlcat/b/top10lists/archive/2008/10/01/top-10-sql-server-integration-services-best-practices.aspx), wonder why recommend to use the hint NOLOCK (point #4). Apart the fact that you could read inconsistent data, there's also the chance to get the error "Could not continue scan with NOLOCK due to data movement." Do you really use it? Thanks in advance

I use NOLOCK only when ordered to. I would prefer to find some other way to reduce contention.Russel Loski, MCT, MCITP Business Intelligence Developer and Database Developer 2008 Blog: http://www.bidn.com/blogs/RussLoski/ Twitter: @sqlmovers

I'm agree with you. In really, really rare cases I use it. That's why I wonder why this could be a best practice, as this article says.