You are facing a standard problem in any server application.
If a connection needs something done and it is taking a long time you are locking up
resources.
You can have another process do the queueing and return to ND without waiting for
completion.
This may create other issues with users.
[EMAIL PROTECTED] wrote:
>Hello,
>
>I am running ND4.1.3 on NT with MS SQL 6.5. I have a stored procedure that
>does multiple inserts (about 20) into a table and it used by 15-100+ users at
>a time. Due to row locking for the inserts, some people are naturally
>queued. However, this is causing performance issues on my ND server because
>of the dB connections. Right now, I do a manual submit of the stored
>procedure (sp.getValue(...) for each input parameter and then sp.execute()).
>Before proceeding, I check for sp.succeeded(). Is there a more efficient way
>to send this information to the dB and release the dB connnections?
>
>Any suggestions would be greatly appreciated.
>
>Thank you in advance,
>
>Sal
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
