Thanks guys.

Edhy beat me to it by a few seconds.

You can set the SqlCommand.Timeout.  The default value is 30, which will cause the SQL Server connector to throw an exception if the command hasn't been completed in 30 seconds.  You can set it to 0, which means "no timeout".  Or you can set it to any number of seconds that you want.

Hi Danny,

Set the timeout to the connection to 0 to allow your sp to run properly.

SqlCommand.Timeout = 0

Edhy Rijo

I have a stored procedure in SQL server which will run for a while. When I call the stored procedure from the application ES returning "Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding"