OE 10.2B and higher.
Is there any reason why I could not run multiple, parallel update statistics commands on different tables?
I've done it. It works.
But I didn't find that it was really worth the effort. Maybe if you've got a db that is really big and the single thread is taking a really long time? But even then I'm guessing your time is dominated by a monster table so the benefits will be smallish.
I was just thinking about databases that have 2-3-4 monster tables. I'm running one now and I realize that the physical box could handle a 2nd update stats in parallel.
Test it and report back!
I have two DBs with some large tables to update stats on and this is on the DEV/TEST box so the disk I/O subsystem is not great. One table with 237M records and a size of 26 Gb took 3h to do a full table/index/column update stats. There is a 45Gb/430M records table running now.
I never tried to "tune" this to make it faster. Is there anything that can be done on the sql side?