Re: locking
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 06/01/04
- Next message: Hai Wu: "SQL Server Log Shipping Destination File Cleanup"
- Previous message: Andrew J. Kelly: "Re: SQL Server 2000 - Unexplained Performance Issue"
- In reply to: Eric.Li: "Re: locking"
- Next in thread: Peter Yeoh: "Re: locking"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Jun 2004 18:16:03 -0400
Eric is correct but I want to make one slight comment. SQL Server never
escalates to a page level lock from a row level. All escalation is always
to table level if it occurs. But it can choose to take out a page or table
level lock in the first place.
-- Andrew J. Kelly SQL Server MVP "Eric.Li" <anonymous@microsoftnews.org> wrote in message news:OMU0VgBSEHA.1392@TK2MSFTNGP09.phx.gbl... > It depends. Default is row level, but optimizer may escalate it to page > or table level locking if it see fit. You can force it to stay at row > level by using query hints. Check query hints in BOL > > -- > Eric Li > SQL DBA > MCDBA > > Dan wrote: > > > How does SS2000 lock by default for a select, update and delete statement. > > Is it row level, page, table? > > > > Thanks, > > > > Dan > > > >
- Next message: Hai Wu: "SQL Server Log Shipping Destination File Cleanup"
- Previous message: Andrew J. Kelly: "Re: SQL Server 2000 - Unexplained Performance Issue"
- In reply to: Eric.Li: "Re: locking"
- Next in thread: Peter Yeoh: "Re: locking"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|