Hi, I have a large application, with a 12GB db. This db is OLTP and reporting (custom reporting, not OLPA) We have had locking/blocking issues, and have been adding WITH(NOLOCK) to all of our reporting queries and most of our OLTP queries. Business decision that dirty reads will not be an issue. We are still having performance issues. The CPU utilization is low, memory is good, # of transactions is good, re-indexing weekly, but we still get slow responses and timeouts in our ASP application. It seems that perormance degrades with usage. e.g. Query 1 on Developement db = 10 seconds, in production takes 40 seconds or more. (and in many cases we get odbc timeouts) So, aside from all the usual responses (separate oltp and reporting solutions, hardware, data partitioning etc) and am wondering if the WITH(NOLOCK) is contributing to the issues. We do see that adding the hint to a single query will make it run faster, but I am wonderint if adding it to ALL the queries is actaully a bad thing ! Does the SQL engine then work differently, and maybe not as efficent by NOT locking ? Everything I have read says that WITH(NOLOCK) will only affect the locking/blocking, but never mentions how/if it affects other aspects of it, or the overall performance. Has anyone experienced this ? Thanks in advance, rob.