InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 06:01:13 GMT20http://www.sqlservercentral.com/Forums/Topic1369366-392-1.aspxFor the nolock, see - [url]http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx[/url]Sun, 07 Oct 2012 03:16:20 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1369366-392-1.aspxThanks guys. I will read up on that.Sat, 06 Oct 2012 23:10:10 GMTvick.ram79http://www.sqlservercentral.com/Forums/Topic1369366-392-1.aspxChapter 6: [url]http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/[/url] (Blocking)Sat, 06 Oct 2012 03:05:38 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1369366-392-1.aspx[quote][b]vick.ram79 (10/6/2012)[/b][hr]yup - the nolock is soo much faster...[/quote]I am not suggesting that you use NOLOCK in your stored procedure.You should investigate why your query is being blocked. You may have a long running or uncommited transaction that is causing a problem.Sat, 06 Oct 2012 01:44:44 GMTMichael Valentine Joneshttp://www.sqlservercentral.com/Forums/Topic1369366-392-1.aspxyup - the nolock is soo much faster...Sat, 06 Oct 2012 00:51:43 GMTvick.ram79http://www.sqlservercentral.com/Forums/Topic1369366-392-1.aspxTry running the statement below. If it runs much faster, your original query is probably being blocked.[code="sql"]select COUNT(*) from TransactionLog with (nolock)[/code]Fri, 05 Oct 2012 22:50:19 GMTMichael Valentine Joneshttp://www.sqlservercentral.com/Forums/Topic1369366-392-1.aspxHave you checked for any blocking?Fri, 05 Oct 2012 20:44:36 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic1369366-392-1.aspxTeam - Friday night is turning bad for me...One of my SPs was taking forever and after a long haul I have nailed it down to one table "TransactionLog" in my db.Even the statement below is taking forever:[code="sql"]select COUNT(*) from TransactionLog[/code]Just not ending... Can anyone tell what could be the reason??I ran a dbcc check:[code="sql"]DBCC CHECKTABLE ("dbo.TransactionLog")[/code]The output was:[code="sql"]DBCC results for 'TransactionLog'.There are 67632 rows in 531 pages for object "TransactionLog".DBCC execution completed. If DBCC printed error messages, contact your system administrator.[/code]Fri, 05 Oct 2012 20:36:10 GMTvick.ram79