Results 1 to 2 of 2
  1. #1
    Join Date
    Dec 2008
    Toronto, Canada

    Unanswered: update, import, load

    I am sorry if I am asking a stupid question, but my developers keep bugging me...

    we are doing data updates in tables. and sometimes it’s 2 records, sometimes - 5000, and sometimes - 900,000. is there any kind of “best practice” at what number of records we should go from using option 1 to option 2 and than to option 3:
    1. update set (few records at the same time);
    2. import with insert_update (most or all records will be updated);
    3. export, update values in export file, load replace;

    Thanks in advance
    DB2 9.5/9.7 on Unix/AIX 6.1/Linux

  2. #2
    Join Date
    Jan 2009
    Zoetermeer, Holland
    Option 3 sounds like an oldfashioned mainframe solution to me. This involves a lot of hassle to be sure that no other process is using that table. When more than 80% of the data has to be changed you could consider it, but if you can find the (processing) time to do the job without the hassle, do it the normal SQL way to be sure and "rollforwardable"..... (you like the new word I just invented?)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts