Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2000 Table Hints Expand / Collapse
Author
Message
Posted Sunday, April 14, 2002 12:00 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, August 14, 2007 1:40 PM
Points: 42, Visits: 1
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/RDyess/tablehints.asp


Post #3581
Posted Thursday, April 15, 2004 3:54 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 12:07 PM
Points: 301, Visits: 792

Nice article, I especially near the end where real world experience is discussed.  I personally would like to see real world comparison between nolock and readpast, but maybe that's another article.  

In some places the article correctly attributes decision-making to the optimizer, but in a few places I think the article misleads by attributing optimization decisions to the Query Analyzer:  "Table Hint May Not Be Used By Query Analyzer", "the query analyzer will often choose ...", "the query analyzer's preference for indexed views...", and "Another reason the query analyzer may ignore...."  Substitute "optimizer" for "Query Analyzer" and problem goes away.




Post #111335
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse