Why not just use a UNION in your stored procedure and just get a single
result set back?
HTH,
Matt
-Original Message-
From: adonis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 11:26 AM
To: [EMAIL PROTECTED]
I have created a stored procedure in Sql Server which uses a cursor
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
Are you looking at the process virtual memory size or the working set
size? These two will give quite a different picture of what your
process is doing. (It's also sometimes a less than exact science
interpreting this stuff, since measuring a process's memory use is not
always that clear cut -
My first question would be for what purpose?
I want a second AppDomain because I want a fresh copy of each of my
singletons. These singletons hold cached data that changes slowly. Note
that I do *not* want to update the cached data in the first AppDomain.
Changing the Web Config file for an
My experiment:
1) 2 AppDomains within one process:
AppDomain A sends AppDomain B 100 messages via Remoting or Socket
AppDomain B sends AppDomain A 100 messages via Remoting or Socket
2) 2 Processes:
Process A send Process B 100 messages via Remoting or Socket
Process B send Process A
Hello
This is my first post and also my first foray into the wonderful world
of .NET Remoting.
I apologise if it's a little long.
I have been experimenting with .NET remoting particularly in the area of
authentication.
I have hosted a simple component in IIS 6 running on Windows 2003 Server
and
The term for these 'levels' is generations. In fact there are 3
generations, numbered 0, 1, and 2. Objects in generation zero are those
which were allocated after the most recent garbage collection to have
completed.
What you say is true - objects that are in generation 0 that are still
in use
