
This option is available in the DBA Cockpit under .
The Monitoring Environment option provides the following features:
Creates logins for monitoring remote databases.
This feature creates a script to be executed on the remote server by a login with sysadmin privileges. The script can be executed directly or copied and executed manually. This feature allows to create a script, which can be executed on the remote server. The connection settings are displayed and the user can change some of them. For example, you can choose the level of trust and the action of the script. The level of trust can be sysadmin privilege, Impersonate dbo, Standard permissions and Restricted permissions. The action of the script can be Initial setup without cleanup, Reinstall monitor infrastructure with preservation of performance history data, Reinstall monitor infrastructure and not preserve performance history data or Uninstall complete monitor environment.
For Solution Manager 7.1, the login setup is done using a wizard in transaction SOLMAN_SETUP. This wizard always uses Restricted permissions as the level of trust. This means that even an SAP user who has full authorizations to DBACOCKPIT in Solution Manager cannot read or modify any data in the ABAP or Java application tables of the remote system.
Executes single or all SQL scripts that are delivered as part of the SAP system.
For more information, see SQL Script Execution Options below.
This screen lists various parameters for the DB monitor. You can modify some of them. To modifythem, enter a new value and press Activate.
Displays the information about the principal used to access SQL Server
Displays the permissions for the login used to connect to the SQL Server
Displays the SAP authorizations for the user who executed the DBACOCKPIT transaction
SQL Script Execution Options
With the SQL scripts you can create SQL Server objects such as stored procedures, user-defined functions, views, and tables. These objects are specific for SAP systems running on SQL Server and are necessary for the ABAP Data Dictionary and the SQL Server monitor functions to work properly.
In older releases, a similar function was part of the ABAP program MSSPROCS.
The following table shows the options that are available with SQL Script Execution
| Option | Description |
|---|---|
|
Execute SQL script(s) |
Executes a single or all script(s) depending on whether you selected Execute all or Execute single SQL script |
|
Execute all |
Executes all scripts |
|
Execute single SQL script |
Executes a single script |
|
SQL Server release |
Displays the current release selection defining the set of SQL scripts to be executed. With this option you cannot execute scripts that are incompatible with the target database release. Make sure that you enter this application directly through the DBA Cockpit navigation menu rather than through SQL script maintenance. In this case, the system picks the correct database release for you. |
|
Script version (source) |
Specifies the version of the SQL script source The version string contains three parts:
|
|
Script version (destination) |
Specifies the field the version, which is currently active on the destination database. The version string contains three parts:
|
|
Functional level |
Allows you to specify the group of SQL scripts to be executed:
|