{\rtf1\ansi\ansicpg1252\deff0\deftab360{\fonttbl{\f0\froman\fprq2\fcharset0 Times New Roman;}{\f1\fswiss Arial;}{\f2\fswiss\fcharset0 Arial;}{\f3\fswiss\fcharset0 Arial;}}
\viewkind4\uc1\pard\lang1033\f0\fs20 Rob,\par
\par
Are you using EIE or AIE? Those are known to open a thread and leave an open a new connection everytime you run a schedule. When you view your Activity Monitor on your MS-SQL Enterprise Manager, you will see loads of open threads associated with the EIE/AIE service if you are using this..\par
\par
If you are using this, a workaround is use a batch job to start the required EIE/AIE service, just prior to running a schedule and stop it a while after the schedule has completed its run. Stopping the service kills the open connection with the MS-SQL database..\par
\par
Joe\par
\f1\par
-----Original Message-----\par
From: Action Request System discussion list(ARSList)\f2 \f1[mailto:[EMAIL PROTECTED] Behalf Of Axton\par
Sent: Sunday, January 27, 2008 11:52 AM\par
To: [EMAIL PROTECTED]
Subject: Re: SQL Service Running at 1.5KB\par
\par
\par
Are the threads configured the same for both environments? Each\f2 \f1 thread has a persistent session with the database; this causes some\f2 \f1 level of overhead on the db side. The overhead varies depending on\f2 \f1 the type of db you are using. I can't really speak too knowledgeably\f2 \f1 about SQL Server, but with Oracle, each session has it's own sql_text\f2 \f1 area, which equates to an almost direct correlation between the number\f2 \f1 of active sessions and memory utilization. You still haven't stated\f2 \f1 what the numbers are a measurement of.\par
\par
Axton Grams\par
\pard\plain\f3\fs20 {\pard\plain\f0\fs18 \line No virus found in this outgoing message.\line Checked by AVG Free Edition. \line Version: 7.5.516 / Virus Database: 269.19.13/1246 - Release Date: 1/27/2008 6:39 PM\line }\par
}
