M
Ma-ke
I am making an insert call from an ASP.NET page to a SQL Server
database using an c# executereader call on a stored proc. When the
server is very busy, a single postback event (from a button click)
often results in duplicate records being inserted into the db. Although
this is difficult to reproduce on a debugging environment, peppering
the code with event log entries has shown that the actual c# code
calling the ExecuteReader method is executing twice. It therefore
appears that the entire page is reloading, but I have not verified
this.
This only appears to happen when the database insert sproc takes a
longer time to execute due to heavy server traffic. Has anyone ever
seen this behavior? Does anyone have any idea as to what could be
causing it?
database using an c# executereader call on a stored proc. When the
server is very busy, a single postback event (from a button click)
often results in duplicate records being inserted into the db. Although
this is difficult to reproduce on a debugging environment, peppering
the code with event log entries has shown that the actual c# code
calling the ExecuteReader method is executing twice. It therefore
appears that the entire page is reloading, but I have not verified
this.
This only appears to happen when the database insert sproc takes a
longer time to execute due to heavy server traffic. Has anyone ever
seen this behavior? Does anyone have any idea as to what could be
causing it?