Re: Blocking issue
From: Wayne Snyder (wayne.nospam.snyder_at_mariner-usa.com)
Date: 12/15/04
- Next message: Wayne Snyder: "Re: Transaction Log Failure"
- Previous message: Grant Merwitz: "DTS ERror Email"
- In reply to: Henry: "Blocking issue"
- Next in thread: AnthonyThomas: "Re: Blocking issue"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 15 Dec 2004 07:49:32 -0500
To add more details, using the default settings for SQLServer, Select
statements get a short read lock. This lock lasts a very short time unless
the select is in a trasaction with Holdlock. In that case the read locks (
called shared locks) are held for the duration of the transaction. These
shared locks will prevent anyone from updating the rows.
-- Wayne Snyder, MCDBA, SQL Server MVP Mariner, Charlotte, NC www.mariner-usa.com (Please respond only to the newsgroups.) I support the Professional Association of SQL Server (PASS) and it's community of SQL Server professionals. www.sqlpass.org "Henry" <Henry@discussions.microsoft.com> wrote in message news:3C18EC8B-1573-4BB3-8EB0-EFD74AAEB4D1@microsoft.com... > Dear Sir/Madam, > > I have run the sp_who2, and found that a process is blocking others processes. > But after I checked the blocker process, it is a SELECT query, which suppose > wouldn't lock any pages/tables, am I right? So, what is happening? > > Many thanks! > > Yours sincerely, > Henry :)
- Next message: Wayne Snyder: "Re: Transaction Log Failure"
- Previous message: Grant Merwitz: "DTS ERror Email"
- In reply to: Henry: "Blocking issue"
- Next in thread: AnthonyThomas: "Re: Blocking issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|