|
|
Posted by ppateel on 01/26/06 00:01
Hi,
First I would like to apologize for cross posting in three groups as
I did not know which one would be the appropriate group. If some one
points me to the correct one I will use that in the future.
I am trying to findout the scalabilty of an user written extended
store procedure. I have created a dll using a C program
(modified/plagarized from some of the examples) . The main function of
this extended SP is to act as a passthru to connect to an third party
ODBC driver. All this is supposed to do is take the passthru sql
statement, userid, passsword and connect to a remote server (IBM 3090
Mainframe in our case) using a system ODBC connection and pass the
returned result set back to the stored procedure calling this extended
SP. I am trying to find out the answers for the following questions.
1. What are the limitations of this approach.
2. What would happen say if 2,000 concurrent calls per minute are made
to the extended SP from the web app.
3. What would happen if this continued for say 4 hours. Will the memory
usage increase to point that will cripple the server assuming there is
no memory leak in the dll.
4. Are there any connection pooling concerns that I should pay
attention to specifically from an Extended SP point of view.
5. Apart from compiling the dll using the "MultiThread" option should I
be using other options to make sure the dll is threadsafe.
SQL server Environment :
OS - Windows 2000 Advanced Server SP4
SQL - SQLServer 2000 Enterprise edition SP3
Hardware - 8 way 2 node cluster with 6Gb RAM
Any help regarding this is greately appreciated.
Prahalad
Navigation:
[Reply to this message]
|