With replica support, one can balance the load of the report execution between the master database and the database replicas. One can define the execution of read-only reports to happen on read-only replicas and keep reports that make changes to the database in master/read-write replicas.
When a user logs into myDBR, the login is done against the database that is defined in The user UI runs against the server that is defined in the Environment settings. Admin can define per report against which server the reports are run. Choices are:
master- Serveer defined in the Environment settings
randomize- myDBR will pick randomly one of the defined replicas
replica- Chosen replica
myDBR disables its internal writes to the database, if the chosen replica has been marked as read-only in the definition. Editable reports will not work against a read-only replica.