Re: MSSQL Stored Procedures Call

[Justin Dearing <zippy1981@xxxxxxxxx>]

Why do you need a queue? Is the issue that the stored procedure can only be
call serially?

Why not submit jobs to run the query and do whatever with the results sets
and output paramaters to a single threaded jobq?

Can you not rewrite the stored procedure so it can be called multiple times
simultaneously? Are you doing something like global ##temp tables in it?

On Thu, Mar 17, 2016 at 8:40 AM Don Brown <DBrown@xxxxxxxxxx> wrote:

> Looking for any suggestions;
>
> I have a call to a stored procedure on a MSSQL server. The function is used
> by multiple users and called multiple times.
>
> My thinking is to create two keyed data queues and a monitor program that
> can start the JVM and create the connection to the MSSQL server, then wait
> on requests on the data queue. A request is then processed and the result
> returned on the second data queue.
>
> Is there a better solution to avoid the overhead of starting the JVM and
> initiating the connection to the MSSQL server for each request?
>
> Thank you for any suggestions
>
> Don
>
> Sent from my iPhone
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.