SQL Server Timeout error on deployment/production server

  • Thread starter Thread starter DotNet User
  • Start date Start date
D

DotNet User

Hello All,

I am facing SQL Server related problem. Here is the scenario:

1. We have a windows application (24x7) that has timer running on the form. The timer interval is set at 3 minutes. On every timer tick, a method is called that executes a stored procedure. On execution of the stored procedure, certain tables are updated, that causes triggers on the tables to run. These triggers are in turn executing a stored procedure and so on resulting in a lot of database activity.

2. We do not have control on the database (tables, triggers etc cannot be modified by us).

3. Also, another C++ application is running in background that constantly pumps data into the database. This application updates many tables at a time in a transaction (and hence holds locks on the database tables).

Issue : After running a single instance of Windows application for about 8-9 hours, the following error was received:
System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.




I am not sure as to what could be the cause of this problem??

This problem is not faced on development server. I am facing this problem only on production server.

Can someone suggest a solution to the above problem or provide valuable tips/new approaches to counter this problem.

I need to solve this problem ASAP. Please reply ASAP.
 
Hi,

Didn't we discuss it already?
Did you try increasing SqlCommand.CommandTimeout property?

--
Miha Markic - RightHand .NET consulting & software development
miha at rthand com

Hello All,
I am facing SQL Server related problem. Here is the scenario:
1. We have a windows application (24x7) that has timer running on the
form. The timer interval is set at 3 minutes. On every timer tick, a method
is called that executes a stored procedure. On execution of the stored
procedure, certain tables are updated, that causes triggers on the tables to
run. These triggers are in turn executing a stored procedure and so on
resulting in a lot of database activity.
2. We do not have control on the database (tables, triggers etc cannot be
modified by us).
3. Also, another C++ application is running in background that constantly
pumps data into the database. This application updates many tables at a time
in a transaction (and hence holds locks on the database tables).

Issue : After running a single instance of Windows application for about 8-9
hours, the following error was received:
System.Data.SqlClient.SqlException: Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not
responding.
 
Back
Top