Re: Executing large result queries

From: pnp (pnp.at.softlab.ece.ntua.gr)
Date: 08/09/04


Date: Mon, 9 Aug 2004 21:43:34 +0300

I'll try to post it there... Thanks anyway.

"Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in
message news:upyMcDjfEHA.708@TK2MSFTNGP09.phx.gbl...
> If you check Books Online, you will find following for the "Audit Logout"
event:
> Duration The approximate amount of time since the user logged in.
>
>
> But the SQL:BatchCompleted are the same, so this indicates that the query
executes in the same time, the added
> time for the logout is the time for the client to process the results
before it can logout from the SQL
> Server.
>
> I.e., the problem is with the client app (at least as far as I can see).
You might want to post this (with
> appropriate details) to an ADO.NET group...
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> "pnp" <pnp.at.softlab.ece.ntua.gr> wrote in message
news:%23LQX4gZfEHA.3016@tk2msftngp13.phx.gbl...
> > well i checked it with the profiler and while the SQL:BatchCompleted
takes
> > about the same amount of time for each execution (~2200) the Audit
Logout is
> > different and when the program slows down it takes numbers up to ~584263
> > while a normal execution takes up to ~20296.
> >
> > What does this mean?
> >
> >
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote
in
> > message news:%23q6Ow0XfEHA.224@TK2MSFTNGP10.phx.gbl...
> > > Start by using Profiler to see if you get the same execution plan
between
> > the executions. Depending on whether
> > > you do or not, you can determine whether this is a SQL Server issue or
a
> > client app issue.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "pnp" <pnp.at.softlab.ece.ntua.gr> wrote in message
> > news:OiAfzBTfEHA.4092@TK2MSFTNGP10.phx.gbl...
> > > > Hi all,
> > > > I've developed an app (C#) that connects to SQL Server 2000 without
> > using
> > > > thread pooling (using SqlConnection) and I run a query that returns
> > ~4000
> > > > tuples each time it runs and displays the results in a listview. The
> > problem
> > > > is that after I run it 3-4 times the results are read very slowly
from
> > the
> > > > DB. The first times the results are displayed in 1-2 secs but the
4,5
> > time
> > > > it takes more than 2 minutes! What am I doing wrong? Are there any
> > > > in-between buffers that need to be emptied?
> > > >
> > > > Thanks,
> > > > -peter
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Relevant Pages

  • Re: Executing large result queries
    ... executes in the same time, ... before it can logout from the SQL ... > Tibor Karaszi, SQL Server MVP ... >> client app issue. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: ENDOFJOB.COM similiar to SYLOGIN.COM and LOGIN.COM
    ... >executes SYLOGIN.COM and LOGIN.COM prior to the submited ... >SYLOGIN.COM executed at the beginning of the batch job. ... >changes to many a command procedure. ... You can redefine LOGOUT, but as the manual goes on to say there is a myriad ...
    (comp.os.vms)
  • Re: running login/logout scripts
    ... > When you logout I am not sure if BASH executes the '.logout' file as ... I think the bash login files are also run every ... I am looking at the Gnome Device Manager. ...
    (Fedora)
  • FormsAuthentication.SignOut() does not appear to remove authentication ticket
    ... After transversing the site, the user clicks on logout which executes the following: ... The transfer hapens, but without asking for re-authentication, WHY? ...
    (microsoft.public.dotnet.framework.aspnet.security)