Download a 30-day trial of RPG2SQL Integrator and you'll be reading and writing SQL Server and calling Stored Procedures in an hour or two.
You should see sub-second response times assuming your SQL Server is fast :-)
http://www.helpsystems.com/rjs
I wrote it so I know it's fast.
Regards,
Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn
------------------------------
message: 4
date: Thu, 17 Mar 2016 22:26:02 +1000
from: Don Brown <DBrown@xxxxxxxxxx>
subject: MSSQL Stored Procedures Call
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
As an Amazon Associate we earn from qualifying purchases.