| Prahalad 2006-01-30, 11:23 am |
| Hi,
We are getting an access violation in an extended stored procedure
occasionally. The details of the environment and stored Proc are below.
Server : Dual Processor with 2Gb of memory
OS : Windows Advanced Server SP4
SQL Server : SQL Server 2000 SP4
Number of instances : 4
Extended Stored proc : Written in C. Connects to a system ODBC DSN
connecting to a third part ODBC driver using ODS and regular call to
srv_paraminfo,SQLCol
Attribute,SQLAllocHa
ndle,SQLExecDirect,S
QLBindCol
etc. Compiled using the Multi-threaded (/MT)option
We are running a stress test to test this extended Stored proc.
The same set of three ODBC SQL statements are called over and over again
(all 3 are stored procedures returning 1 row of data). This AV does not
happen every time. Last time it happened after about 6000 transaction(4
transactions per min) and after 2500 transaction(8 transactions per
min). To minimize the disruptions to the instance that contains the
database the Extended stored proc is defined in a separate instance and
this is called from the actual database using a linked server and 4 part
naming convention "LinkedServer.Database.Owner.ExtendedStoredProc". Is
it possible that it is running into some threadsafe issues. We are not
using any fancy functions except the srv_ functions and ODBC functions.
We have monitored the memory used by the instance and observed that
there is no dramatic increase in the memory allocation for the instance.
Any help in trying to solve/identify this is greatly appreciated.
I can attach the source code if it is needed.
Prahalad
|