|
-
Jul 17th, 2008, 03:34 PM
#1
[RESOLVED] [2008] SQLcommand Async methods worth using?
I'm working on a project that needs quite a bit of interaction with an SQL database, mainly loading and saving data to and from DGVs on my forms.
I noticed that instead of running the standard synchronous methods of the SQLCommand class you can also run some Async ones too such as BeginExecuteNonQuery() and BeginExecuteReader(). So I did a quick bit of reading up on the MSDN site and to be honest it looks like quite a bit of work learning how exactly to implement this along with the EndExecuteReader() etc methods to actually return the results. Then once I had figured out how to use them I would obviously have to replace all the existing synchronous methods I have already written. So I was wondering if anyone here has used these methods much in the past? I'm not dragging huge amounts of data from the SQL tables so load times in my application are pretty small as it is but as I'm sure you all know even a small delay between screens (the UI blocking I mean) can give users cause to label your software as "slow" and "unresponsive"...
So basically, my question is has anyone used these methods previously and if so is it a lot of work implementing them or should I give it a go just to cut out all possible blocks of my UI thread?
Ta
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|