F5 to load balance MS Sql Servers

Now that I see your scope I may be able to help while keeping it simple. We had/have a similar issue.

 

 

We created a new table or DB where we kept the "switch" (0 or 1) AFter the SUCCESSFUL data load the process would

 

flip the switch and the downstream applications, which were programmed to look for the switch, then knew what DB to go to.

 

The "old" DB (populated with the previous data load) then sits idle waiting for the next load (and is availble as some redundancy)