Showing posts with label number. Show all posts
Showing posts with label number. Show all posts

Friday, March 9, 2012

I need your general opinion on "Lock: Timeout"

Hi
In the process of investigating a poor performing application, I've ran
number of traces on our SQL server. In these traces, I can see that
there're a high number of EventClass 27 - Lock: Timout.
I'd assume that in theory I shouldn't have any lock timeouts, but is
that also the case in the real world?
The trace has run for an hour, and if I look in the data afterwards, I
have 11583 records of eventclass 27 out of a total of approx 1,6 million
records in the trace file.
I know that these figures may not tell a lot since it depends on many
factors, but is it "normal" to see such a high number of timouts?
What are your experience from other situations?
Regards
Steen"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:ex8CB4x0FHA.1564@.tk2msftngp13.phx.gbl...
> Hi
> In the process of investigating a poor performing application, I've ran
> number of traces on our SQL server. In these traces, I can see that
> there're a high number of EventClass 27 - Lock: Timout.
> I'd assume that in theory I shouldn't have any lock timeouts, but is that
> also the case in the real world?
> The trace has run for an hour, and if I look in the data afterwards, I
> have 11583 records of eventclass 27 out of a total of approx 1,6 million
> records in the trace file.
> I know that these figures may not tell a lot since it depends on many
> factors, but is it "normal" to see such a high number of timouts?
> What are your experience from other situations?
>
Unless the application has set a finite lock timeout, locks won't time out
at all. That event should tell you what object the lock is on. But more
importantly look at the Lock: Acquired event for events with a long duration
(it's in milliseconds). This is the surest sign of locking problems.
David|||David Browne wrote:
> "Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
> news:ex8CB4x0FHA.1564@.tk2msftngp13.phx.gbl...
>> Hi
>> In the process of investigating a poor performing application, I've ran
>> number of traces on our SQL server. In these traces, I can see that
>> there're a high number of EventClass 27 - Lock: Timout.
>> I'd assume that in theory I shouldn't have any lock timeouts, but is that
>> also the case in the real world?
>> The trace has run for an hour, and if I look in the data afterwards, I
>> have 11583 records of eventclass 27 out of a total of approx 1,6 million
>> records in the trace file.
>> I know that these figures may not tell a lot since it depends on many
>> factors, but is it "normal" to see such a high number of timouts?
>> What are your experience from other situations?
> Unless the application has set a finite lock timeout, locks won't time out
> at all. That event should tell you what object the lock is on. But more
> importantly look at the Lock: Acquired event for events with a long duration
> (it's in milliseconds). This is the surest sign of locking problems.
> David
>
I can see that I haven't included the "Lock Acquired" event in my trace,
so I'll have to run a new one with this included.
I've looked further in my current trace data, but there're no Object on
the "Lock: Timeout" event, so that doesn't tell me much.
I'll check it further when I have the new trace data and see if I can
get something out of the lock acquired event.
Regards
Steen|||Steen Persson (DK) wrote:
> I can see that I haven't included the "Lock Acquired" event in my
> trace, so I'll have to run a new one with this included.
> I've looked further in my current trace data, but there're no Object
> on the "Lock: Timeout" event, so that doesn't tell me much.
> I'll check it further when I have the new trace data and see if I can
> get something out of the lock acquired event.
> Regards
> Steen
Lock:Timeout will track internal type timeouts that are not really a
problem. If memory serves, you can use Lock:Timeout, but only worry
about those events that are raised with a Duration > 0. Also look for
Attention events, SQL:BatchCompleted/RPC:Completed events for a high
level analysis of SQL performance. Include SQL:StmtCompleted and
SP:StmtCompleted for more detail.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com

I need to pass data entered /created on the first page to the next page and populate the next pa

Hello I have a project that uses a large number of MS Data access pages created in Access 2003 and runs on MS SQL2005.

When I am on lets say my client, (first page in a series) data access page and I have completed the fields in the (DAP), I am directing my users to the next step of the registration process by means of a hyperlink to another Data access page in the same web but in a linked or sometimes different table.


I need to pass data entered /created on the first page to the next page and populate the next page with some data from the first page / table. (like staying on the client name and ID when i go to the next page)


I also need the first data access page to open and display a blank or new record. Not an existing record. I will also be looking to creata a drop down box as a record selector.


Any pointers in the right direction would be appreciated.
I am some what new to data access pages so a walk through would be nice but anything you got is welcome. Thanks Peter…

YOu will have to establish some Session management, either completly on the client (cookies) or on the Server (with a session cookie) or via URL states. Look for Session Management and you will find many directions in google.

HTH, Jens K. Suessmeyer.

http://www.sqlserver0205.de
|||Thanks I now have a lot to read, I do already have a username password script running fine i need to carry information foward like shopping cart total! this is https also so html post would be fine i am looking for some examples or walk through's I am sure the answer is right in front of me it usualy is!

I need to pass data entered /created on the first page to the next page and populate the nex

Hello I have a project that uses a large number of MS Data access pages created in Access 2003 and runs on MS SQL2005.

When I am on lets say my client, (first page in a series) data access page and I have completed the fields in the (DAP), I am directing my users to the next step of the registration process by means of a hyperlink to another Data access page in the same web but in a linked or sometimes different table.


I need to pass data entered /created on the first page to the next page and populate the next page with some data from the first page / table. (like staying on the client name and ID when i go to the next page)


I also need the first data access page to open and display a blank or new record. Not an existing record. I will also be looking to creata a drop down box as a record selector.


Any pointers in the right direction would be appreciated.
I am some what new to data access pages so a walk through would be nice but anything you got is welcome. Thanks Peter…

YOu will have to establish some Session management, either completly on the client (cookies) or on the Server (with a session cookie) or via URL states. Look for Session Management and you will find many directions in google.

HTH, Jens K. Suessmeyer.

http://www.sqlserver0205.de
|||Thanks I now have a lot to read, I do already have a username password script running fine i need to carry information foward like shopping cart total! this is https also so html post would be fine i am looking for some examples or walk through's I am sure the answer is right in front of me it usualy is!

I need to have a drill down...

Ok here it is:
this row is always visible:
dealernumber dealername dealerlineageid
+(show a drilldown under each dealernumber if a number in the table
this additional row comes from contains any matching string in their
number with "dealerlineageid" number on the row above them.
In other easier words, hide all rows below each dealer, unless there is
a matching number in the dealerlineageid number in the details row.
Thanks,
TrintInsert a group under the detail row. The detail row should just contain
a cell with value Fields!dealernumber.Value. Insert a group under that,
and group by dealername (and dealerlineageid if you wish). Then, in the
group header (and footer if necessary) rows, put all necessary values.|||It looks like a hide expression on the field containing the string I
need to compair with would be more efficient. But how would the
expression be if if is needing to query the string since the string
contains more than one dealer number, but also has the one I need to
display what I am originally hiding?
Thanks,
TRint
Bassist695 wrote:
> Insert a group under the detail row. The detail row should just
contain
> a cell with value Fields!dealernumber.Value. Insert a group under
that,
> and group by dealername (and dealerlineageid if you wish). Then, in
the
> group header (and footer if necessary) rows, put all necessary
values.