We have a customer that has set up their environment such that the SR DB (YF DB) is being replicated, however, some tables are not in sync and have left them out of replication. What we would like to know is in a disaster recovery situation, the following tables will not be in sync:
In the case that the application was made to point to the DB where the above tables are not in sync with the previous one, would it cause any issues?
Based on what I know:
- It shouldn't prevent the services from starting up, and the application will still work
- Existing reports may not work
Can you help me confirm?