JamesMorrison (9/17/2012)
I understand what you are saying with the update trigger directly to the new partition table.The problem I see with that is if an update to the original table happens, but that row is not yet on the partitioned version of the table, there is nothing for the trigger to update. That was the thinking with having a 3rd table track those changes, then have a brief outage to sync the updates and swap the table names.
Assuming you are still migrating the data into the shadow table it doesnt matter if the row is there or not on an update. You still update the live row.