Re: Slow performance after restarting
From: Eric Hirst (s.p.a.r.k.y.d.o.o.d.l.e.d.o.o_at_y.a.h.o.o)
Date: 02/18/04
- Next message: Louis Davidson: "Re: Order by clause..."
- Previous message: Keith Kratochvil: "Re: Grouping"
- In reply to: Tim: "Re: Slow performance after restarting"
- Next in thread: Tim: "Re: Slow performance after restarting"
- Reply: Tim: "Re: Slow performance after restarting"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 18 Feb 2004 11:32:18 -0800
I don't think it's a network issue, this happens all on a single box.
(Although I think I get the same effect when the QA client is on a different
box.)
Shutting off Norton AV doesn't affect it.
Changing connection pooling settings (60 seconds, 10 seconds, no pooling)
has no effect (Thanks Tom, we had not thought about pooling.)
Not machine dependent, can repro on XP & Win2K, latest SR's, single proc,
dual proc, and dual + hyperthreading.
Next step: look at the log files. They are very large for the db in
question, on the order of .5 to 1.5 GB. But
DBCC SHRINKDATABASE and DBCC SHRINKFILE don't seem to affect the behavior
either.
-Eric
"Tim" <Tim@NoSpam> wrote in message
news:%23J6u4Re9DHA.2368@TK2MSFTNGP11.phx.gbl...
> Eric,
>
> If the problem was the other way around, I would be thinking DNS or
perhaps
> WINS issues (NT / etc).
> May be that'll kick brain cells in the right direction....
>
> Is the ODBC connection right for the network? What does server network
> config and client network config say?
> Any firewall software in sight? IE Nortons...
>
> - Tim
>
> "Eric Hirst" <s.p.a.r.k.y.d.o.o.d.l.e.d.o.o@y.a.h.o.o> wrote in message
> news:#y0cpAb9DHA.1636@TK2MSFTNGP12.phx.gbl...
> > We have a service application which typically starts up in 1-3 seconds.
> Most
> > of this time is spent running SQL and DML against SQL Server 2000, SP3,
> via
> > ODBC. The service is registered to depend on SQL Server.
> >
> > When I restart SQL Server, our app sometimes takes 1-3 seconds, but
> > occasionally takes several minutes. The difference? It's only slow when
> > there is a secondary client, such as Query Analyzer, running during this
> > process. That is, I can:
> >
> > (1) Start SQL Server
> > (2) Start Query Analyzer and connect to SQL Server
> > (3) Stop SQL Server
> > (4) Start our service, which runs DML and SQL against SQL Server.
> > (4.1) YAAAAWN Wait several minutes, with the CPU almost idle, while our
> > service runs its initial DDL and SQL.
> >
> > I can then stop and restart our service several times. In each case,
it's
> > very slow. But then I can:
> >
> > (5a) Close Query Analyzer
> > -or-
> > (5b) Execute some SQL in Query Analyzer
> >
> > and suddenly our service jumps back to life, stopping and starting
> snappily
> > in response to the SCM, pushing the CPU hard for a second or two each
> time.
> >
> > Any idea what's going on here? Ideally, we'd like to find a programatic
> way
> > to make SQL Server "forget" about Query Analyzer and any other client
> > connections whenever it is cycled. Note that this is a test environment
> and
> > we don't actually care if these clients crash or otherwise misbehave.
> >
> > Thanks, Eric
> >
> > --
> > Eric Hirst, SSE
> >
> > Sorry, I don't want to test my company's spam filters.
> > Please follow up to newsgroup, or send mail to the
> > following address, which I check occasionally:
> >
> > s-p-a-r-k-y-d-o-o-d-l-e-d-o-o
> > y-a-h-o-o
> > c-o-m
> >
> >
>
>
- Next message: Louis Davidson: "Re: Order by clause..."
- Previous message: Keith Kratochvil: "Re: Grouping"
- In reply to: Tim: "Re: Slow performance after restarting"
- Next in thread: Tim: "Re: Slow performance after restarting"
- Reply: Tim: "Re: Slow performance after restarting"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
