Thanks to everyone for the replies. I've done everything short of calling the garbage collector which has been suggested against both in print and verbally. As for the SQL solution Russ suggest below, I think my collection of SQL stored procs that gets called to create my reports its more complicated than my SQL abilities to create on my own into one massive stored proc....I also need to make these into html emails, nicely formatted...something System.web.mail does very nicely for me to send out to from anywhere between 0 - 300 people per day. This isn't spam by any means. Its internal to our organization. :)
It appears the memory usage depends on the quantity of the emails sent out that day but I'm destorying (setting to nothing) all of the DataSets and DataReaders used. As mentioned in a pervious post, it likes 7MB just to exists as a service in the Service Manager running a 24 hour timer. Courtney Date: Wed, 30 Jul 2003 09:37:38 -0700 From: Russell McClure <[EMAIL PROTECTED]> Subject: Re: windows service memory footprint Courtney, Just a thought (I'm assuming you are using SQL Server): you could actually leverage the SQL Server Agent to do what you describe. That way you wouldn't even need your own service. All you would need to do is to create a Job under the SQL Server Agent and specify the times that you want it to launch. Then add steps to the job that call the stored procedures and send emails etc. This would all be written in T-SQL. Anyway, if this sounds interesting, let me know and I can give you more detail if you want. Russ ===== Courtney Smith [EMAIL PROTECTED]
