|
I have a data access process with multiple consecutive processes
The other is a very long stored procedure that displays transactions.
A company's test machine is exactly the same as the customer's, and the configuration is the same.
When testing in the company, even if you wait a few tens of seconds, those processes will eventually perform well.
But at the client, once waiting for 1 second, it immediately said that a deadlock had occurred, sacrificing a minimum transaction.
The timeout setting of the database is the same as the timeout setting of iis, which is the default value. That problem should not occur at all.
Does anyone encounter this similar problem to me, please enlighten me |
|