 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
VB Forum / Database Access / May 2006Q: DataAdaptor Update
Hi I was wondering if anybody could give me some advice on why I feel that the updates in my application feel "slow". The application I've written downloads from an SQL Server Database, stores this data in a DataSet, values are changed and then I use the Update command to write any changes back to the database. This all works fine. However, this updating takes longer than I expected. I've noted online that "Note that an adapter will update the database row by row (i.e. one UPDATE command will be sent for each modified row), this might be slow if there are many rows to be updated." Is there any way to avoid this? In addition, I've just the CommandBuilder to configure the DataAdaptors. Will this cause a significant delay? If so, how can I get round it? Any help will be most appreciated. Thanks in advance G > In addition, I've just the CommandBuilder to configure the DataAdaptors. > Will this cause a significant delay? If so, how can I get round it? Yes you are right. CommandBuilder is very bad solution for that. You must configure DataAdapter manually. Give UPDATE, INSERT, DELETE commands and parameters manually. Hi Am I right in thinking that the delay is generated because the command builder is called every time an update is made? G >> In addition, I've just the CommandBuilder to configure the DataAdaptors. >> Will this cause a significant delay? If so, how can I get round it? > > Yes you are right. CommandBuilder is very bad solution for that. > You must configure DataAdapter manually. > Give UPDATE, INSERT, DELETE commands and parameters manually. > Am I right in thinking that the delay is generated because the command > builder is called every time an update is made? I don't know, but without builder, update/insert is much faster. Hi Linas Is this because the command builder adds "unnecessary" code i.e. it isn't particularly efficient? G >> Am I right in thinking that the delay is generated because the command >> builder is called every time an update is made? > > I don't know, but without builder, update/insert is much faster. > Is this because the command builder adds "unnecessary" code i.e. it isn't > particularly efficient? I think, that you can see what builder done for your update. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.