Home Forums SQL Server 2008 SQL Server Newbies Adding new varchar (30) field to table causes stored procedure to take 10 times more time RE: Adding new varchar (30) field to table causes stored procedure to take 10 times more time

  • JeeTee (12/9/2014)


    Where did you read nolock is deprecated?

    Not that I'm encouraging use of nolock, but I see it's deprecated in from clauses in updates and inserts, but not straight selects. Unless I'm misinterpreting this:

    http://msdn.microsoft.com/en-us/library/ms143729.aspx%5B/quote%5D

    This could be getting lost in interpretation

    From http://msdn.microsoft.com/en-us/library/ms187373.aspx

    It states

    For UPDATE or DELETE statements: This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.

    I am not sure if that means do not include with SELECTs in all future work so I am not taking any chances. Of course this knowing that NOLOCK is not something you use in production code at all to begin with.

    ----------------------------------------------------