Keep one connection open for log

I am using SQL 7. If I open one connection for long, I notice that as I keep
running more SQL statement my I/O and CPU Usage keep growing. Even though I
am done with the connection not running any statement I still see those
resouces being used.
Is it a bug in SQL 7 or it happens with 2000 also. Is it a memory leak ?
Please help.
Hi
Look up 'Connection Pooling' in BOL.
The MDAC driver keeps the connection open by default 120 seconds, and if
another query, to the same saver, using the same credentials comes along on
the same client machine., it just re-uses the existing connection.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Astros" <Astros@.discussions.microsoft.com> wrote in message
news:64E68C08-BACE-44A0-9301-2476AA954CD3@.microsoft.com...
> I am using SQL 7. If I open one connection for long, I notice that as I
keep
> running more SQL statement my I/O and CPU Usage keep growing. Even though
I
> am done with the connection not running any statement I still see those
> resouces being used.
> Is it a bug in SQL 7 or it happens with 2000 also. Is it a memory leak ?
> Please help.
|||I do not agree with you at all. For SQL 7 it is not true. I saw connections
stays there as long as I do not discoonect.
You have not answered any thing of my question. My bad luck is no body else
going to answer this question.
"Astros" wrote:

> I am using SQL 7. If I open one connection for long, I notice that as I keep
> running more SQL statement my I/O and CPU Usage keep growing. Even though I
> am done with the connection not running any statement I still see those
> resouces being used.
> Is it a bug in SQL 7 or it happens with 2000 also. Is it a memory leak ?
> Please help.
|||Hi
Well, then give us more information. Give us outputs of sp_who2 over
intervals and run profiler at the same time to see what is being submitted
to SQL Server. You might find that there are requests being submitted. There
is no known bug where counters increase themselves for no reason.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Astros" <Astros@.discussions.microsoft.com> wrote in message
news:52DB2055-CAE1-42CE-A106-C55E1422D918@.microsoft.com...
> I do not agree with you at all. For SQL 7 it is not true. I saw
connections
> stays there as long as I do not discoonect.
> You have not answered any thing of my question. My bad luck is no body
else[vbcol=seagreen]
> going to answer this question.
> "Astros" wrote:
keep[vbcol=seagreen]
though I[vbcol=seagreen]
|||Hi Mike,
I don't mean to be rude the other day. My application using one connection
and doing same kind of activities again and again. Several hundred time doing
same insert for a different record. It is not cursor as far as SQL server
concern. From within the application it is repeating.
Another situation is: I open query analyser and start using it for different
type of select or updat etc. Using same connection. I see that counter for
I/O and CPU keep increasing. Not necessarily I am using more resouce
consuming SQL but I never see those resouceses being released. Unless I killl
the connection.
Aziz
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Well, then give us more information. Give us outputs of sp_who2 over
> intervals and run profiler at the same time to see what is being submitted
> to SQL Server. You might find that there are requests being submitted. There
> is no known bug where counters increase themselves for no reason.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Astros" <Astros@.discussions.microsoft.com> wrote in message
> news:52DB2055-CAE1-42CE-A106-C55E1422D918@.microsoft.com...
> connections
> else
> keep
> though I
>
>