A checklist for fixing .NET applications to SQL Server timeout problems and improve execution time

Question

A checklist for improving execution time between .NET code and SQL Server. Anything from the basic to weird solutions is appreciated.

Code:

Chan

Answer 1

In the past some of my solutions have been:

1. Fix the default time out settings of the sqlcommand:

   Dim myCommand As New SqlCommand("[dbo].[spSetUserPreferences]", myConnection)

   myCommand.CommandType = CommandType.StoredProcedure

   myCommand.CommandTimeout = 120

2. Increase connection timeout string:

   Data Source=mydatabase;Initial Catalog=Match;Persist Security Info=True;User ID=User;Password=password;Connection Timeout=120

3. Increase transaction time-out in sql-server 2005

   In management studio’s Tools > Option > Designers Increase the “Transaction time-out after:” even if “Override connection string time-out value for table designer updates” checked/unchecked.

4. Convert dynamic stored procedures into static ones

5. Make the code call a stored procedure instead of writing an inline sql statement in the code.