This section explain the configuration to allow the execution of reports on secondary database server.

# 1 Define database secondary server

The seconary database server must be defined at the database servers master data.

# 2 Set database secondary as mirror

The seconary database server must be configured as mirror of primary database server.

# 3 Database connection group

The database connection group needs to have permission on the secondary server. To do that, the "Access" value must be "Allow secondary".

Field Description
Access

Determines if the group has permission to connect to the secondary database server. In this case the execution of objects could be redirected to the secondary servers.

Show secondary

Determines if the folder of database secondary server is visible on the application explorer.

# 4 SQL objects

There are some features that are required for objects to be executed on secondary servers.

1. Objects that can be executed on the secondary server are only objects type "Read only".

2. There is not allowed to do DDL operations on secondary server:

Copy
26097: Operation is not valid on a secondary server.
140: ISAM error: operation illegal on a DR Secondary

Only temporary tables "with no log" are allowed.

# 5 Redirection

If the database server has a mirror defined, the user belongs to a connection group that allows access to the secondary server and the object is of the type "read only", when the user invokes this object, the system automatically redirects the Secondary server execution.