Strategy for loading tables and usage of views

We have several large volumes of data to be loaded under INFX 7.30; this will totally replace several existing tables. During the loading time, the users should still have normal access to the database but a drop in performance is acceptable if not too substantial. Only a brief stop (less than 10 minutes) is OK. Th envisaged strategy is (disk space is not a problem): - create a new database without logging - in this database, create the tables and fill them using DBLOAD (followed by constraints, indexes, update stats...) - enable unbuffered logging for this database - disable user access from the production database - in the production database, rename the old tables - in the production database, create views for the new tables from the new database (with identical names as the production tables being replaced; create view as ... select * from ...)- enable user access to the production database Does this sound a viable solution ? If not, any recommendations ? If yes, are there impacts on performance due to the fact that the tables will not be accessed directly within the database but indirectly via a view to a table form a distinct database ? Thanks for any advice.