July 26, 2012 at 10:44 am
Recently I discovered that all .net applications are causing two callls for every stored procedure. So when I run the SQL profiler it shows:
rpc:completed some stored procedure
rpc:completed some stored procedure
rpc:completed exec sp_reset_connection
I would have never realized the issue because I always use if exists or if not exists around my insert/update statements. I have a new database developer and they were only doing inserts for a function and didn't put the if not exists so it would break (duplicate key - they generated the uniqueidentifier; otherwise it would have created two records using an autonumber.)
This happens on several servers and all .net applications. previous clasic asp pages use the sql:batch command.
Has anyone else run into this problem and is there a way to fix it?
This might be a connection issue from .net we are using system.data.sqlclient.sqlconnection and system.data.sqlclient connection strings and both result in the dual stored procedure calls.
This is not a page reload issue because this happens every time and we step through the code and the code only runs once.
July 30, 2012 at 9:25 am
Sounds odd. Can you please post more from the trace? Including the text data from the entries for the proc calls?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply