[Edit: meant to ask - is the full-load only or CDC as well. CDC makes rename even harder if not impossible]
I understand the desire to load to temp tables and switch when done.
This is not a new request and many years ago an attempt was made to implement this for SQLserver target based on a specific customer request. I suspect the code is still there controlled by an advance, internal, parameter loadToTempTables.
The basic required actions are clear: on successful table full-load, drop the original table, make sure the temp table protections are as they should be for the real table, rename.
The error handling and timing challenges are less clear, similar to a direct full load but just less clear. While it worked, the customer at that time decided NOT to use it in production and with that the availability remained limited to (5) SQLserver family targets and was never 'advertised', only visible by figuring out how to see internal parameters, guess at their usage and verify with reptasks and target db SQL LOGS.
You could (should?) consider an feature request. Why not. Just don't hold your breath while waiting.
Instead figure out how to use a Replicate API (preferably the Enterprise Manager, but REPCTL command will work also and make yourself a script looking at "full_load_completed","full_load_start","full_load_end" (and possibly full_load_counters) from GetTaskDetails or more likely GetTableStatuses looking for per-table "table_full_load_info" and status. A good bit of work, but only done every minute or so and computers don't mind.
Or one could scan the reptask log(s) for table load completed messages every so often remembering where one left off and mindful of logs being rolled.
Details you depend on whether managing a full load for all tables, for some, and whether some table have foreign keys and are best renamed when all all done (something Replicate could/would not know).
Hope this helps some!
Hein.
