Of course it will impact a system using that table, but not significant I expect and the production system should handle it. If you are committing like this, then you can kill the script at any time and not lose any work. The query to find the next IDs to update is probably the slowest part of this depending on what indexes you have.
- Batch update million records in prd DB Yi Sun
- Re: Batch update million records in prd DB Michael Lewis
- Re: Batch update million records in prd DB Yi Sun
- Re: Batch update million records in prd DB Michael Lewis
- Re: Batch update million records in prd... Yi Sun
- Re: Batch update million records i... Michael Lewis
- Re: Batch update million records in prd DB Kristjan Mustkivi