I was reading up on this article:
And I was wondering in the article it was about updating the tables of your database but not a complete new insert. Once a day a import runs to import every table (again). I was wondering is option 2 mentioned in the article not better then one single import run??Here
is your link again, this time in click-able form.
The gist of the article is that row-by-row updates using the OLEDBCOMMAND component are slow, but running such updates in parallel is less slow. It's definitely not fast, whatever you do.
Finding a set-based solution usually leads to the best performance (though you may need to consider batching updates and deletes to avoid excess tlog pressure).
Back to your question, which is a little unclear, to be honest. You seem to be asking whether it is better to UPDATE than to INSERT? I don't see how you can replace one with the other, unless your INSERT is preceded by a DELETE, perhaps.
What do you mean by 'single import run'?
Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this
If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.
Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.