Re: waitresource

From: Kalen Delaney (replies_at_public_newsgroups.com)
Date: 07/24/04 

Date: Fri, 23 Jul 2004 17:57:38 -0700

Great.. thanks for the feedback! 

--
HTH
----------------
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hassan" <fatima_ja@hotmail.com> wrote in message
news:OyUr#EQcEHA.1568@TK2MSFTNGP10.phx.gbl...
> 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 ?
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: PAE VS SQL Server AWE
    ... "Mike Epprecht " wrote in message ... > Mike Epprecht, Microsoft SQL Server MVP ... >> Kalen Delaney:-P) that when you shrink the kernel mode address space ...
    (microsoft.public.sqlserver.server)
  • Re: Protecting database
    ... I meant the metadata is available to anyone who can connect! ... "Kalen Delaney" wrote in message ... > SQL Server MVP ...
    (microsoft.public.sqlserver.security)
  • Re: Force 0?
    ... > Pro SQL Server 2000 Database Design ... >> If that is the case, try using GROUP BY ALL MSNumber ... >> Kalen Delaney ... >> SQL Server MVP ...
    (microsoft.public.sqlserver.programming)
  • Re: Can view accept parameters
    ... Tibor Karaszi, SQL Server MVP ... >>Kalen Delaney ... >>> thks & rdgs ...
    (microsoft.public.sqlserver.server)
  • Re: IX lock on a table
    ... How are you seeing the IX lock? ... the same spid that has the IX lock. ... SQL Server MVP ... "Kalen Delaney" wrote in message ...
    (microsoft.public.sqlserver.server)