SQR Runner » Logins/Databases

SQR Runner 4 Pro allows to define up to 20 "Logins" each containing both SQR related settings as well as database settings. Benefits are the ease of use and execution of programs as SQR development usually involves different databases and also different sets of SQR directories: each Login is capable of representing a specific environment.

• For each open file a separate Login can be easily selected/changed during development
• A selected Login is used when running a SQR program or executing a SQL statement
• The supported database system for SQR programs requires - except for debugging - an already installed SQR reports engine, provided/included by e.g. Hyperion, PeopleSoft or ADP
• For SQL execution different types of databases are natively supported, such as Oracle, SQL Server, DB2, Sybase or regular ODBC connection. Note: special RDBMS-specific language constructs such as PL/SQL for Oracle may not be supported.
• Execution of a SQR program may either occur locally(*) or on a remote server via automated Telnet session or REXEC/RSH command
• SQR Runner remembers the last selected Login for each open file
• Each Login contains details such as SQR search directories, SQR engine- and file location/naming, Remote Server Execution (RSE) and repository support settings
  The RSE command line is a dynamic template which allows flexible command line creation for the remote server
• Support for dynamic logfile naming to include database name, program name or a timestamp. This is helpfull to e.g. build a history of logfiles to be compared later by the developer

Example display of the "Novice Mode" tab configuration:

Example of a Remote Server Execution configuration:

Above mentioned trademarks are property of their respective owners.
(*) local SQR execution requires - except for debugging - an existing SQR reports engine which is not included