SqlCommand object - set it and forget it?

Question

I'm using SqlClient.SqlCommand object to run a few stored procs on my db. Normally when I run these manually via Query Analyzer they take up to 15 minutes to complete.

So obviously when I run them using the SqlCommand object I get a SqlCommand timeout.

I know I could set the timeout property to a very high number, but I'm wondering if alternatively there's a way to just kickoff the procs and disconnect. I don't need a return value.

Any suggestions? I'm not interested in optimizing the processing time of each sp here, just trying to determine if there's a 'set it and forget it' option.

Here's the content of the SqlCommand object:

using (SqlCommand cmd = new SqlCommand(@"update tbl_SYS_DATE set RPT_DATE = @inputDate
                                                    exec sp_Get_Bp_Data1
                                                    exec sp_Get_Bp_Data2          
                                                    exec sp_Get_Bp_Data3
                                                    exec sp_channel_data1
                                                    exec sp_channel_data2
                                                    exec sp_channel_data3
                                                    ", con))

score 5 · Accepted Answer · answered Oct 29 '09 at 15:11

5

You can use an async method, like BeginExecuteNonQuery. The timeout is ignored for that.

answered Oct 29 '09 at 15:11

Jason

1,119
8
9

+1 - beat me by 22 seconds (but no link, so who really won?:-) ) – Harper Shelby Oct 29 '09 at 15:13
If you use this method, make sure you don't put your SqlConnection in a using clause or the connection will be disposed before the command is done executing. – Aheho May 12 '14 at 18:42

score 4 · Answer 2 · answered Oct 29 '09 at 15:12

4

Use the asynchronous method call BeginExecuteNonQuery. From the MSDN page

The CommandTimeout property will be ignored during asynchronous method calls such as BeginExecuteReader.

answered Oct 29 '09 at 15:12

Harper Shelby

16,475
2
44
51

score 0 · Answer 3 · answered Oct 29 '09 at 15:11

0

You could run that code from a background thread. You could look into the BackgroundWorker object.

answered Oct 29 '09 at 15:11

Ryan Alford

7,514
6
42
56

SqlCommand object - set it and forget it?

3 Answers3