CPU Using - Audit Logout

I have a VP app. that uses some queries from SQL Server 2000.
I'm noticing in SQL Profiler that the event "Audit Logout" is using alot of
cpu at times.
How can I decrease these CPU times ?Keep the connection open.
"Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
news:O9QSMS9wDHA.1996@.TK2MSFTNGP12.phx.gbl...
> I have a VP app. that uses some queries from SQL Server 2000.
> I'm noticing in SQL Profiler that the event "Audit Logout" is using alot
of
> cpu at times.
> How can I decrease these CPU times ?
>|||> Keep the connection open.
i cant keep the connection open.
Is there any other solution for this problem.
> "Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
> news:O9QSMS9wDHA.1996@.TK2MSFTNGP12.phx.gbl...
> > I have a VP app. that uses some queries from SQL Server 2000.
> >
> > I'm noticing in SQL Profiler that the event "Audit Logout" is using alot
> of
> > cpu at times.
> > How can I decrease these CPU times ?
> >
> >
>|||My guess is that it is cleaning up a lot of server side cursors when it
spikes the cpu. Can you tell if the times when it happens if any of the
queries used server side over client side?
--
Andrew J. Kelly SQL MVP
"Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
news:O9QSMS9wDHA.1996@.TK2MSFTNGP12.phx.gbl...
> I have a VP app. that uses some queries from SQL Server 2000.
> I'm noticing in SQL Profiler that the event "Audit Logout" is using alot
of
> cpu at times.
> How can I decrease these CPU times ?
>|||We have a VB application. Over Timer control, we have run SQL queries. These
query types are, sometimes SELECT sometimes UPDATE. Everty time that app.
run, these queries executed. Every Connecion's Cursor Location is Client
Side. When we check SQL Profiler, Audit Logout events's CPU has been
increased. I think this is caused for operating systems CPU usage. How can
we decrease that high CPU usage or How can we decrease Audit Logout usage ?
Thanks a lot.
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:OFpNTl%23wDHA.1908@.TK2MSFTNGP10.phx.gbl...
> My guess is that it is cleaning up a lot of server side cursors when it
> spikes the cpu. Can you tell if the times when it happens if any of the
> queries used server side over client side?
> --
> Andrew J. Kelly SQL MVP
>
> "Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
> news:O9QSMS9wDHA.1996@.TK2MSFTNGP12.phx.gbl...
> > I have a VP app. that uses some queries from SQL Server 2000.
> >
> > I'm noticing in SQL Profiler that the event "Audit Logout" is using alot
> of
> > cpu at times.
> > How can I decrease these CPU times ?
> >
> >
>|||The logout is probably not using much time at all. More of a total. I know
this is true of duration, and I am pretty sure it is true of CPU. It is not
a perfect addition of all of the other rows, so I might be wrong, but I am
sure that the logout operation is not one of the more costly operations.
However, if applications are making and breaking too many connections, it
can become an issue.
--
----
--
Louis Davidson (drsql@.hotmail.com)
Compass Technology Management
Pro SQL Server 2000 Database Design
http://www.apress.com/book/bookDisplay.html?bID=266
Note: Please reply to the newsgroups only unless you are
interested in consulting services. All other replies will be ignored :)
"Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
news:O9QSMS9wDHA.1996@.TK2MSFTNGP12.phx.gbl...
> I have a VP app. that uses some queries from SQL Server 2000.
> I'm noticing in SQL Profiler that the event "Audit Logout" is using alot
of
> cpu at times.
> How can I decrease these CPU times ?
>|||But it's a cumulative count of the resources used for the lifetime of the
connection so whilst it may appear high it should be roughly the sum of the
CPU the connection used executing queries etc. Thus it being high or low
does not mean much, it's generally more interesting to look at those
statements that consumed most of the resources during the lifetime of the
connection if you see what I mean
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
news:O9QSMS9wDHA.1996@.TK2MSFTNGP12.phx.gbl...
> I have a VP app. that uses some queries from SQL Server 2000.
> I'm noticing in SQL Profiler that the event "Audit Logout" is using alot
of
> cpu at times.
> How can I decrease these CPU times ?
>|||Yes as Jasper points out this is a cumlative counter and will increase over
time as expected.
--
Andrew J. Kelly SQL MVP
"Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
news:%23L1$80%23wDHA.2316@.TK2MSFTNGP10.phx.gbl...
> We have a VB application. Over Timer control, we have run SQL queries.
These
> query types are, sometimes SELECT sometimes UPDATE. Everty time that app.
> run, these queries executed. Every Connecion's Cursor Location is Client
> Side. When we check SQL Profiler, Audit Logout events's CPU has been
> increased. I think this is caused for operating systems CPU usage. How can
> we decrease that high CPU usage or How can we decrease Audit Logout usage
?
>
> Thanks a lot.
>
>
> "Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
> news:OFpNTl%23wDHA.1908@.TK2MSFTNGP10.phx.gbl...
> > My guess is that it is cleaning up a lot of server side cursors when it
> > spikes the cpu. Can you tell if the times when it happens if any of the
> > queries used server side over client side?
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
> > news:O9QSMS9wDHA.1996@.TK2MSFTNGP12.phx.gbl...
> > > I have a VP app. that uses some queries from SQL Server 2000.
> > >
> > > I'm noticing in SQL Profiler that the event "Audit Logout" is using
alot
> > of
> > > cpu at times.
> > > How can I decrease these CPU times ?
> > >
> > >
> >
> >
>|||Ok. Firstly, Thank you very much. From Now on, what sholud we do ? Have you
any idea ?
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:O8v2zj$wDHA.1500@.TK2MSFTNGP12.phx.gbl...
> But it's a cumulative count of the resources used for the lifetime of the
> connection so whilst it may appear high it should be roughly the sum of
the
> CPU the connection used executing queries etc. Thus it being high or low
> does not mean much, it's generally more interesting to look at those
> statements that consumed most of the resources during the lifetime of the
> connection if you see what I mean
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Tahir Ozmen" <tahirozmen(at)hotmail.com> wrote in message
> news:O9QSMS9wDHA.1996@.TK2MSFTNGP12.phx.gbl...
> > I have a VP app. that uses some queries from SQL Server 2000.
> >
> > I'm noticing in SQL Profiler that the event "Audit Logout" is using alot
> of
> > cpu at times.
> > How can I decrease these CPU times ?
> >
> >
>

CPU Pegging

I have
Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
I am noticing the processors are pegging quite a bit, cpu for the
sqlservr.exe process is running around 50% constantly with lots of pegs up
to 100%. Is there something I should be looking at before I throw more
hardware at it? Is this normal, knew sql server sucked memory but not the
cpu. The memory for the process is around 1.6 gig. It is a production
machine so it is hit pretty hard during the day.
John"John Cantley" <jcstrider@.hotmail.com> wrote in message
news:uc2glj1vDHA.2304@.TK2MSFTNGP12.phx.gbl...
> I have
> Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
> I am noticing the processors are pegging quite a bit, cpu for the
> sqlservr.exe process is running around 50% constantly with lots of pegs up
> to 100%. Is there something I should be looking at before I throw more
> hardware at it? Is this normal, knew sql server sucked memory but not the
> cpu. The memory for the process is around 1.6 gig. It is a production
> machine so it is hit pretty hard during the day.
> John
>|||Well, you might want to look at profiler and see if there are specific
queries that can be better tuned or rewritten
"John Cantley" <jcstrider@.hotmail.com> wrote in message
news:u4sV1n1vDHA.1424@.tk2msftngp13.phx.gbl...
> "John Cantley" <jcstrider@.hotmail.com> wrote in message
> news:uc2glj1vDHA.2304@.TK2MSFTNGP12.phx.gbl...
> > I have
> >
> > Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
> >
> > I am noticing the processors are pegging quite a bit, cpu for the
> > sqlservr.exe process is running around 50% constantly with lots of pegs
up
> > to 100%. Is there something I should be looking at before I throw more
> > hardware at it? Is this normal, knew sql server sucked memory but not
the
> > cpu. The memory for the process is around 1.6 gig. It is a production
> > machine so it is hit pretty hard during the day.
> >
> > John
> >
> >
>|||Oh, and as an aside, if your pegging CPU, one thing to look for is cursors.
"John Cantley" <jcstrider@.hotmail.com> wrote in message
news:u4sV1n1vDHA.1424@.tk2msftngp13.phx.gbl...
> "John Cantley" <jcstrider@.hotmail.com> wrote in message
> news:uc2glj1vDHA.2304@.TK2MSFTNGP12.phx.gbl...
> > I have
> >
> > Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
> >
> > I am noticing the processors are pegging quite a bit, cpu for the
> > sqlservr.exe process is running around 50% constantly with lots of pegs
up
> > to 100%. Is there something I should be looking at before I throw more
> > hardware at it? Is this normal, knew sql server sucked memory but not
the
> > cpu. The memory for the process is around 1.6 gig. It is a production
> > machine so it is hit pretty hard during the day.
> >
> > John
> >
> >
>|||| I have
|
| Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
|
| I am noticing the processors are pegging quite a bit, cpu for the
| sqlservr.exe process is running around 50% constantly with lots of pegs up
| to 100%. Is there something I should be looking at before I throw more
| hardware at it? Is this normal, knew sql server sucked memory but not the
| cpu. The memory for the process is around 1.6 gig. It is a production
| machine so it is hit pretty hard during the day.
--
Hi John,
The most important question you need to ask yourself as a DBA: are your
users complaining about slowness or lack of responsiveness? If not, then
things are fine. The old adage goes, "if it ain't broke, don't fix it."
High CPU utilisation, as long as it's not always running at 100%, is
actually a GOOD THING. That means that the CPU, the most expensive
component of a computer system, is doing it's job. If you see CPU spiking
to 100% on occasion, that means there are no bottlenecks in your computer
system.
Hope this helps,
--
Eric Cárdenas
SQL Server support|||Eric,
Ok just wondering then.
I have a smaller server that runs our website content and customer order
data, I coded the application and made heavy use of stored procedures,
triggers and such. The cpu is typically under 10% and mem usage is about 1/2
gig and connections are usually in the 50 range. The site is heavily used
for order tracking and other stuff.
The one that is causing me problems is a bigger faster machine with two
processors, I have no control of the frontend application that is used in
our production process, it uses 0 stored procedures, 0 triggers, nothing
nada zilch. I am thinking that since this is true then I am not getting a
good rate of the sql statements compiled, since so many varying queries are
hitting it. I have also noticed 3 connections opening just upon startup of
the application. Couldn't these factors account for the higher cpu usage. I
preformed a backup on it and noticed that the cpu usage dropped to a lower
rate. I am thinking that maybe the transactions are left dangling by the 3rd
party product and the backup process terminates them.
john
"Eric Cardenas" <ecard@.anonymous.com> wrote in message
news:pfOA846vDHA.3532@.cpmsftngxa07.phx.gbl...
> | I have
> |
> | Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
> |
> | I am noticing the processors are pegging quite a bit, cpu for the
> | sqlservr.exe process is running around 50% constantly with lots of pegs
up
> | to 100%. Is there something I should be looking at before I throw more
> | hardware at it? Is this normal, knew sql server sucked memory but not
the
> | cpu. The memory for the process is around 1.6 gig. It is a production
> | machine so it is hit pretty hard during the day.
> --
> Hi John,
> The most important question you need to ask yourself as a DBA: are your
> users complaining about slowness or lack of responsiveness? If not, then
> things are fine. The old adage goes, "if it ain't broke, don't fix it."
> High CPU utilisation, as long as it's not always running at 100%, is
> actually a GOOD THING. That means that the CPU, the most expensive
> component of a computer system, is doing it's job. If you see CPU spiking
> to 100% on occasion, that means there are no bottlenecks in your computer
> system.
> Hope this helps,
> --
> Eric Cárdenas
> SQL Server support
>