Show TOC

Creating or Selecting DBCON Entries for All Remote Monitoring DestinationsLocate this document in the navigation structure

Procedure
  1. Call the DBA Cockpit.
  2. In the system landscape toolbar, choose DB Connections.
  3. Choose Add.

    The screen Database Connection Details appears.

  4. In the Connection Name field, specify the name of the connection.
    Note

    This name is a unique ID that you can choose freely except for names that are reserved by SAP for generated connections. These can be, for example, administrator connections.

  5. Specify the database connection attributes as follows:
    1. In the Database System field, specify the name of the database platform.
    2. In the Connection Maximum field, enter an appropriate value. This value limits the number of database connections that are currently held by the SAP system. The SAP system does not let you exceed this limit.
    3. In the Connection Optimum field, enter an appropriate value. This value is a more flexible limit that can be exceeded.
    4. If you want the connection to be mandatory for the SAPsystem, select Permanent Connection. This parameter defines the availability of the database connection.

      It is then handled like the local default connection, that is, the work process of the SAP system can only run if this database connection is available for the work process.

      Caution

      Set this parameter only if this connection is absolutely required to run your SAP system.

    5. In the User Name field, enter the name of the SQL Server login.

      The SAP multiconnect mechanism allows both integrated security logins and the use of SQL Server authentication. If you use Windows security, leave this field empty.

      Note

      You can use the Login setup screen in the DBA Cockpit. Choose Configuration → Monitoring Environment to create an SQL script to run in the remote SQL Server database, and to create the necessary SQL Server logins to monitor the remote SQL Server database. In the latest releases, you can also execute this script directly from the Login setup using a SQL login, which temporarily connects and executes the script. The login must have sysadmin privileges.

    6. In the Password field, enter a password for the SQL server Login.

      If you have decided to use integrated security, leave this field empty.

  6. In the Connection Parameters table, specify the following database-specific attributes:
    Attribute Description

    Database Server (Instance)

    Name of the remote database server

    Database Name

    Name of the remote database

    Object Source Name

    This database schema contains all SAPdatabase monitor objects, for example, stored procedures, user-defined functions, and tables. They implement the low-level database monitor functions.

    Note

    To take advantage of future enhancements in remote MSSQL monitoring, we strongly recommend that you use the object source schema name SAPMonitor (the schema name is case-sensitive).

    Database User

    Entry is not allowed for this field. It is not used for remote monitoring.
    Note

    To support upcoming new connection parameters and for support scenarios, you might have to add connection parameters in an unchecked raw format. To be able to do so, choose Guided Mode <-> Expert Mode and switch to the expert mode. In the expert mode, you can enter connection parameters as a string instead of using the guided mode. However, we do not recommend that you use the expert mode.

  7. Save your entries.

Result

The database is now automatically cataloged. As soon as the connection is specified, the DBA Cockpit connects automatically to the newly added database system and displays data on the System Data tab page.