Re: waitresource
From: Hassan (fatima_ja_at_hotmail.com)
Date: 07/23/04
- Next message: Derek Ruesch: "Re: maximum number of views"
- Previous message: Mike John: "Re: SQL7 MULTI CPU ENABLED?"
- In reply to: Kalen Delaney: "Re: waitresource"
- Next in thread: Kalen Delaney: "Re: waitresource"
- Reply: Kalen Delaney: "Re: waitresource"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 23 Jul 2004 15:06:01 -0700
On page 80, should it be "Process 52 requests an EXCLUSIVE lock on a key
that process 56 already has a share lock on."
Also on lock escalation, i think in your Inside SQL server 2000, you talked
more about the algorithm used such as if lockx ? x or so on and so forth. It
would have been nice to see that
Also on page 46, you state that in Chapter 6, you'll discuss how we might be
able to tell if a lock escalation has actually caused blocking problems.. I
dont see anything in Chapter 6
And the deadlock detection algo was not so clear to me...
"Kalen Delaney" <replies@public_newsgroups.com> wrote in message
news:ec5PQmNcEHA.1764@TK2MSFTNGP10.phx.gbl...
> Please send any errors to me.
> I might be able to do an update. That's supposed to be one of the
advantages
> of an ebook, but since it got sold to a different publisher, I'm not sure
> what the procedure is.
>
> Thanks
> --
> HTH
> ----------------
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
>
> "Hassan" <fatima_ja@hotmail.com> wrote in message
> news:OD37MCNcEHA.3716@TK2MSFTNGP11.phx.gbl...
> > btw Kalen, in your trobleshooting guide on Locking and Blocking, do you
> have
> > an error log for errors in that publication if any noted someplace ?
> >
> > "Kalen Delaney" <replies@public_newsgroups.com> wrote in message
> > news:%23%23pt%23LIcEHA.796@TK2MSFTNGP09.phx.gbl...
> > > If the waittype is 0, you are not waiting for anything. The
lastwaittype
> > is
> > > just the last thing you were waiting for, no matter how long ago.
> > >
> > > PAGELATCH usuallly means you are waiting for I/O to complete.,
> > >
> > > Pages are identified by DB ID: File # and Page #. So the last thing
that
> > > process waited on was IO in tempdb, file 1 page 216.
> > >
> > > Why are you concerned about this process?
> > >
> > > --
> > > HTH
> > > ----------------
> > > Kalen Delaney
> > > SQL Server MVP
> > > www.SolidQualityLearning.com
> > >
> > >
> > > "Hassan" <fatima_ja@hotmail.com> wrote in message
> > > news:uINqr2HcEHA.1356@TK2MSFTNGP09.phx.gbl...
> > > > I have a waittype of 0x0000
> > > > lastwaittype of PAGELATCH_UP
> > > > and waitresource as 2:1:216
> > > >
> > > > How exactly do i read that waitresource ? What is 2, 1 and 216 ?
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Derek Ruesch: "Re: maximum number of views"
- Previous message: Mike John: "Re: SQL7 MULTI CPU ENABLED?"
- In reply to: Kalen Delaney: "Re: waitresource"
- Next in thread: Kalen Delaney: "Re: waitresource"
- Reply: Kalen Delaney: "Re: waitresource"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|