Our production database includes a table that is at about 100 million records and will likely get to a billion records before too long. Every other table is small--less than a million records.
The large table depends on the small tables. Individual records are calculated from the small tables and can only be properly interpreted using the context the small tables provide.
We want copies of the small tables for use in staging and testing. We also want them for interpretation of archived versions of the large table. It would be easy to get and maintain these copies if the large table weren't in the production db, so it's tempting to move that table somewhere else. However, we want the systems that interact with the large table to have up-to-date information on the small tables.
Is there a nice way to move the large table out of the production database while maintaining its access to updates on the small tables that are in the production database?