I am not suggesting to do this but I don’t think there would be any performance hits to those using the Table while it is being ‘updated’.
Remember the Table is loaded into memory by the engine so even if you make a change via the GUI the change is not immediate to the engines using the Table.
While there is I/O activity, the Table is only referenced on first use and loaded into memory – a purge caches refreshes the Tables. I don’t think there would be any I/O conflict once the Table is loaded.
I would suspect if one were to do this one would first make a copy of the table and make changes to the copy. Then rename the table files (saving the old one for audit purposes – remember Revisions does not track changes made outside the configurtion tool). Then a purge caches would need to take place for the Table to be refreshed. Unfortunately one cannot refresh just certain objects so all Tables, etc. being used at the level of refreshment will be refreshed. Maybe some objects not wanted to be refreshed just then.
With the exception of the purging caches, all of the above should be able to be accomplished via Tcl (the purge caches via an exec inside the Tcl proc).
Not knowing exaclty what this table is used for, it is difficult to make a single recommendation. There are many methods to keep ‘tables’ updated depending on the use of the Table and other business considerations.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.