Re: row vs page locking...

From: ben brugman (ben_at_niethier.nl)
Date: 09/07/04 

Date: Tue, 7 Sep 2004 14:05:59 +0200

Hello Kalen,

Although I have read the Inside and
the Hands-On SQL server 2000 Troubleshooting :Locking and Blocking.

The last several times and specific for locking and blocking caused
by selects only. I must say I never found a clear indication that
a select on a single row in one table could be 'causing' a deadlock.
(In combination with another transaction doing updates on that
one single row).

If that is in your book or Hands-On, it would be a help if you could
point this out to me.

Thanks for your books,
greetings,
ben brugman

"Kalen Delaney" <replies@public_newsgroups.com> wrote in message
news:#sS#MsClEHA.1652@TK2MSFTNGP09.phx.gbl...
> So reread the locking chapter!
> :-)
>
> --
> HTH
> ----------------
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
>
> "Randall Sell" <randall@bytewise.nospam.com.au> wrote in message
> news:RUR_c.20882$D7.8300@news-server.bigpond.net.au...
> > Thanx Kalen. You book actually sits next to my desk 24/7 :)
> >
> > -randall
> >
> > Kalen Delaney wrote:
> >
> > > Hi Randall
> > >
> > > The complete storage engine was rewritten for SQL Server 7. I worked
for
> the
> > > Sybase Corporation for many years (starting with their version 2), in
> > > training and tech support, and I taught the high-end performance
tuning
> and
> > > internals classes.
> > >
> > > When I started working with MS SQL Server, the architectures were
almost
> > > identical and the smallest unit of locking was the page. But when SQL
7
> came
> > > out, almost everything had to be relearned from an core engine
> perspective.
> > > Yes, there is true row level locking.
> > >
> > > Maybe the person you heard was referring to a pseudo-row-locking
> introduced
> > > in SQL Servfer 6.5, but that was just because they couldn't rewrite
the
> > > whole engire for that version. For SQL 7, they did.
> > >
> > > I even wrote a book about it. If you want all the gory internal
details,
> > > check out Inside SQL Server 7 and/or Inside SQL Server 2000.
> > >
>
>

Relevant Pages

  • Re: Error 3155- Is there no solution?
    ... You might want to look at all processes that use the Materials table - ... Whatever is creating the conflict is most likely locking the table to ... How could anyone use SQL Server in a useful way if tables ... the end of the day to append any records that weren't already in the main ...
    (microsoft.public.access.externaldata)
  • Re: row vs page locking...
    ... so they automatically escalate to page level locks. ... 'Lock Escalation' - see Books Online. ... SQL Server 2005 is going to have a Snapshot ... Good old fashioned locking is less sexy, but I find, more productive! ...
    (microsoft.public.sqlserver.server)
  • Re: Record Locking with SQL Server tables and Access db Client
    ... The reason you don't get the same kind of locking with SQL Server as ... When a user starts to edit a record via the form, ... With SQL Server tables there is only a warning when the second person ... eliminate the ODBC usage at this time is not feasible. ...
    (microsoft.public.sqlserver.odbc)
  • Re: row edited by more than one user at same time
    ... >updating" or sthing like this. ... What you are experiencing is the SQL server default of Optimistic locking. ... Depending on how the ADO Update Criteria property is set the error you are ...
    (borland.public.delphi.database.ado)
  • Re: row vs page locking...
    ... whether SQL Server really did row locking. ... > the Hands-On SQL server 2000 Troubleshooting:Locking and Blocking. ... >> Kalen Delaney ... >>>> internals classes. ...
    (microsoft.public.sqlserver.server)