Hi,
Is there any documentation on LATCH_EX waittypes. I can't find much on the
subject.
Thanks.http://sqldev.net/misc/WaitTypes.htm
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:%23na11e89DHA.1804@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Is there any documentation on LATCH_EX waittypes. I can't find much on the
> subject.
> Thanks.
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:etgJRu89DHA.1504@.TK2MSFTNGP12.phx.gbl...
> http://sqldev.net/misc/WaitTypes.htm
Thanks, but I've seen that one & that's the only one I could find!|||Well there isn't a whole lot that I know of. What seems to be the problem?
Maybe if you describe it we can help.
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:%23sfW1C99DHA.1116@.TK2MSFTNGP09.phx.gbl...
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:etgJRu89DHA.1504@.TK2MSFTNGP12.phx.gbl...
> Thanks, but I've seen that one & that's the only one I could find!
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:udLJab99DHA.2532@.TK2MSFTNGP09.phx.gbl...
> Well there isn't a whole lot that I know of. What seems to be the
problem?
> Maybe if you describe it we can help.
We've got some asp based websites that connect to SQL Server Databases.
One of the asp sites was upgraded with a new set of code and now there are a
large number of LATCH_EX waits when we look at current activity in
Enterprise Manager.
The CPU load on the database server is only about 50% but all the websites
that connect to the database server are running slowly.
We have tried increasing the amount of memory available to SQL Server from
1GB to 2GB but that didn't help.
If we stop that website, the LATCH_EX problems go away, however, if we stop
a different website, the problems also go away.
So it's all a little puzzling.|||What about the disk queues on the drive where the log file resides? Check
to ensure they are low and if not you may consider moving the log files to
their own Raid 1 array. How about the tables them selves? Do you have
clustered indexes on most of them? Do you use a lot of text or image
columns?
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:eIdt4U%239DHA.3636@.TK2MSFTNGP10.phx.gbl...
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:udLJab99DHA.2532@.TK2MSFTNGP09.phx.gbl...
> problem?
> We've got some asp based websites that connect to SQL Server Databases.
> One of the asp sites was upgraded with a new set of code and now there are
a
> large number of LATCH_EX waits when we look at current activity in
> Enterprise Manager.
> The CPU load on the database server is only about 50% but all the websites
> that connect to the database server are running slowly.
> We have tried increasing the amount of memory available to SQL Server from
> 1GB to 2GB but that didn't help.
> If we stop that website, the LATCH_EX problems go away, however, if we
stop
> a different website, the problems also go away.
> So it's all a little puzzling.
>
Showing posts with label latch_ex. Show all posts
Showing posts with label latch_ex. Show all posts
Monday, March 26, 2012
LATCH_EX documentation
Hi,
Is there any documentation on LATCH_EX waittypes. I can't find much on the
subject.
Thanks.http://sqldev.net/misc/WaitTypes.htm
--
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:%23na11e89DHA.1804@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Is there any documentation on LATCH_EX waittypes. I can't find much on the
> subject.
> Thanks.
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:etgJRu89DHA.1504@.TK2MSFTNGP12.phx.gbl...
> http://sqldev.net/misc/WaitTypes.htm
Thanks, but I've seen that one & that's the only one I could find!|||Well there isn't a whole lot that I know of. What seems to be the problem?
Maybe if you describe it we can help.
--
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:%23sfW1C99DHA.1116@.TK2MSFTNGP09.phx.gbl...
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:etgJRu89DHA.1504@.TK2MSFTNGP12.phx.gbl...
> > http://sqldev.net/misc/WaitTypes.htm
> Thanks, but I've seen that one & that's the only one I could find!
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:udLJab99DHA.2532@.TK2MSFTNGP09.phx.gbl...
> Well there isn't a whole lot that I know of. What seems to be the
problem?
> Maybe if you describe it we can help.
We've got some asp based websites that connect to SQL Server Databases.
One of the asp sites was upgraded with a new set of code and now there are a
large number of LATCH_EX waits when we look at current activity in
Enterprise Manager.
The CPU load on the database server is only about 50% but all the websites
that connect to the database server are running slowly.
We have tried increasing the amount of memory available to SQL Server from
1GB to 2GB but that didn't help.
If we stop that website, the LATCH_EX problems go away, however, if we stop
a different website, the problems also go away.
So it's all a little puzzling.|||What about the disk queues on the drive where the log file resides? Check
to ensure they are low and if not you may consider moving the log files to
their own Raid 1 array. How about the tables them selves? Do you have
clustered indexes on most of them? Do you use a lot of text or image
columns?
--
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:eIdt4U%239DHA.3636@.TK2MSFTNGP10.phx.gbl...
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:udLJab99DHA.2532@.TK2MSFTNGP09.phx.gbl...
> > Well there isn't a whole lot that I know of. What seems to be the
> problem?
> > Maybe if you describe it we can help.
> We've got some asp based websites that connect to SQL Server Databases.
> One of the asp sites was upgraded with a new set of code and now there are
a
> large number of LATCH_EX waits when we look at current activity in
> Enterprise Manager.
> The CPU load on the database server is only about 50% but all the websites
> that connect to the database server are running slowly.
> We have tried increasing the amount of memory available to SQL Server from
> 1GB to 2GB but that didn't help.
> If we stop that website, the LATCH_EX problems go away, however, if we
stop
> a different website, the problems also go away.
> So it's all a little puzzling.
>sql
Is there any documentation on LATCH_EX waittypes. I can't find much on the
subject.
Thanks.http://sqldev.net/misc/WaitTypes.htm
--
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:%23na11e89DHA.1804@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Is there any documentation on LATCH_EX waittypes. I can't find much on the
> subject.
> Thanks.
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:etgJRu89DHA.1504@.TK2MSFTNGP12.phx.gbl...
> http://sqldev.net/misc/WaitTypes.htm
Thanks, but I've seen that one & that's the only one I could find!|||Well there isn't a whole lot that I know of. What seems to be the problem?
Maybe if you describe it we can help.
--
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:%23sfW1C99DHA.1116@.TK2MSFTNGP09.phx.gbl...
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:etgJRu89DHA.1504@.TK2MSFTNGP12.phx.gbl...
> > http://sqldev.net/misc/WaitTypes.htm
> Thanks, but I've seen that one & that's the only one I could find!
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:udLJab99DHA.2532@.TK2MSFTNGP09.phx.gbl...
> Well there isn't a whole lot that I know of. What seems to be the
problem?
> Maybe if you describe it we can help.
We've got some asp based websites that connect to SQL Server Databases.
One of the asp sites was upgraded with a new set of code and now there are a
large number of LATCH_EX waits when we look at current activity in
Enterprise Manager.
The CPU load on the database server is only about 50% but all the websites
that connect to the database server are running slowly.
We have tried increasing the amount of memory available to SQL Server from
1GB to 2GB but that didn't help.
If we stop that website, the LATCH_EX problems go away, however, if we stop
a different website, the problems also go away.
So it's all a little puzzling.|||What about the disk queues on the drive where the log file resides? Check
to ensure they are low and if not you may consider moving the log files to
their own Raid 1 array. How about the tables them selves? Do you have
clustered indexes on most of them? Do you use a lot of text or image
columns?
--
Andrew J. Kelly
SQL Server MVP
"Freddy" <noemail@.noemail> wrote in message
news:eIdt4U%239DHA.3636@.TK2MSFTNGP10.phx.gbl...
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:udLJab99DHA.2532@.TK2MSFTNGP09.phx.gbl...
> > Well there isn't a whole lot that I know of. What seems to be the
> problem?
> > Maybe if you describe it we can help.
> We've got some asp based websites that connect to SQL Server Databases.
> One of the asp sites was upgraded with a new set of code and now there are
a
> large number of LATCH_EX waits when we look at current activity in
> Enterprise Manager.
> The CPU load on the database server is only about 50% but all the websites
> that connect to the database server are running slowly.
> We have tried increasing the amount of memory available to SQL Server from
> 1GB to 2GB but that didn't help.
> If we stop that website, the LATCH_EX problems go away, however, if we
stop
> a different website, the problems also go away.
> So it's all a little puzzling.
>sql
Latch wait time
Does anyone know the potential causes of a high average latch wait time
(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
not many inserts, client side cursors.
If the client side cursors are not detached from the main data source, that
could do it. Also, just the network traffic load to get it into a
scrollable client side cursor could cause excess latches.
What does you estimated execution plan look like?
Sincerely,
Anthony Thomas
"Bob S" <noone@.nowhere.com> wrote in message
news:uhNTPu4yEHA.1652@.TK2MSFTNGP11.phx.gbl...
> Does anyone know the potential causes of a high average latch wait time
> (12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at
40%,
> not many inserts, client side cursors.
>
|||You may want to monitor memory (vs disks) for this. You can
find explanations in the Latch_x section of the following
article:
http://www.sqldev.net/articles/WaitTypes.htm
-Sue
On Mon, 15 Nov 2004 22:22:52 -0500, "Bob S"
<noone@.nowhere.com> wrote:
>Does anyone know the potential causes of a high average latch wait time
>(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
>not many inserts, client side cursors.
>
(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
not many inserts, client side cursors.
If the client side cursors are not detached from the main data source, that
could do it. Also, just the network traffic load to get it into a
scrollable client side cursor could cause excess latches.
What does you estimated execution plan look like?
Sincerely,
Anthony Thomas
"Bob S" <noone@.nowhere.com> wrote in message
news:uhNTPu4yEHA.1652@.TK2MSFTNGP11.phx.gbl...
> Does anyone know the potential causes of a high average latch wait time
> (12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at
40%,
> not many inserts, client side cursors.
>
|||You may want to monitor memory (vs disks) for this. You can
find explanations in the Latch_x section of the following
article:
http://www.sqldev.net/articles/WaitTypes.htm
-Sue
On Mon, 15 Nov 2004 22:22:52 -0500, "Bob S"
<noone@.nowhere.com> wrote:
>Does anyone know the potential causes of a high average latch wait time
>(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
>not many inserts, client side cursors.
>
Latch wait time
Does anyone know the potential causes of a high average latch wait time
(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
not many inserts, client side cursors.If the client side cursors are not detached from the main data source, that
could do it. Also, just the network traffic load to get it into a
scrollable client side cursor could cause excess latches.
What does you estimated execution plan look like?
Sincerely,
Anthony Thomas
"Bob S" <noone@.nowhere.com> wrote in message
news:uhNTPu4yEHA.1652@.TK2MSFTNGP11.phx.gbl...
> Does anyone know the potential causes of a high average latch wait time
> (12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at
40%,
> not many inserts, client side cursors.
>|||You may want to monitor memory (vs disks) for this. You can
find explanations in the Latch_x section of the following
article:
http://www.sqldev.net/articles/WaitTypes.htm
-Sue
On Mon, 15 Nov 2004 22:22:52 -0500, "Bob S"
<noone@.nowhere.com> wrote:
>Does anyone know the potential causes of a high average latch wait time
>(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
>not many inserts, client side cursors.
>
(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
not many inserts, client side cursors.If the client side cursors are not detached from the main data source, that
could do it. Also, just the network traffic load to get it into a
scrollable client side cursor could cause excess latches.
What does you estimated execution plan look like?
Sincerely,
Anthony Thomas
"Bob S" <noone@.nowhere.com> wrote in message
news:uhNTPu4yEHA.1652@.TK2MSFTNGP11.phx.gbl...
> Does anyone know the potential causes of a high average latch wait time
> (12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at
40%,
> not many inserts, client side cursors.
>|||You may want to monitor memory (vs disks) for this. You can
find explanations in the Latch_x section of the following
article:
http://www.sqldev.net/articles/WaitTypes.htm
-Sue
On Mon, 15 Nov 2004 22:22:52 -0500, "Bob S"
<noone@.nowhere.com> wrote:
>Does anyone know the potential causes of a high average latch wait time
>(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
>not many inserts, client side cursors.
>
Latch wait time
Does anyone know the potential causes of a high average latch wait time
(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
not many inserts, client side cursors.If the client side cursors are not detached from the main data source, that
could do it. Also, just the network traffic load to get it into a
scrollable client side cursor could cause excess latches.
What does you estimated execution plan look like?
Sincerely,
Anthony Thomas
"Bob S" <noone@.nowhere.com> wrote in message
news:uhNTPu4yEHA.1652@.TK2MSFTNGP11.phx.gbl...
> Does anyone know the potential causes of a high average latch wait time
> (12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at
40%,
> not many inserts, client side cursors.
>|||You may want to monitor memory (vs disks) for this. You can
find explanations in the Latch_x section of the following
article:
http://www.sqldev.net/articles/WaitTypes.htm
-Sue
On Mon, 15 Nov 2004 22:22:52 -0500, "Bob S"
<noone@.nowhere.com> wrote:
>Does anyone know the potential causes of a high average latch wait time
>(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
>not many inserts, client side cursors.
>
(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
not many inserts, client side cursors.If the client side cursors are not detached from the main data source, that
could do it. Also, just the network traffic load to get it into a
scrollable client side cursor could cause excess latches.
What does you estimated execution plan look like?
Sincerely,
Anthony Thomas
"Bob S" <noone@.nowhere.com> wrote in message
news:uhNTPu4yEHA.1652@.TK2MSFTNGP11.phx.gbl...
> Does anyone know the potential causes of a high average latch wait time
> (12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at
40%,
> not many inserts, client side cursors.
>|||You may want to monitor memory (vs disks) for this. You can
find explanations in the Latch_x section of the following
article:
http://www.sqldev.net/articles/WaitTypes.htm
-Sue
On Mon, 15 Nov 2004 22:22:52 -0500, "Bob S"
<noone@.nowhere.com> wrote:
>Does anyone know the potential causes of a high average latch wait time
>(12-20 sec) for LATCH_EX? Total average disk queue depth << 1, CPU at 40%,
>not many inserts, client side cursors.
>
Subscribe to:
Posts (Atom)