E User Permissions for Database Snapshot Monitoring

This section documents the permission requirements for the database snapshot monitoring capability. These steps are only necessary if you have configured the agent to monitor a database. You may modify permissions on an existing account or create a new account with the required permissions. Refer to the platform that is specific to your database.

MS SQL Server 7/Server 2000

Follow the instructions in this section to set permissions for the user account on an MS SQL Server 2000 Database (SQL Server Standard Edition 7.0) or MS SQL Server 2000 Database (SQL Server Enterprise Edition 2000).

Object Permissions

At a minimum, the user account for database monitoring must have SELECT permissions for the following objects:

• <database>.dbo.sysusers

• <database>.dbo.sysobjects

• <database>.dbo.syscolumns

• <database>.dbo.systypes

• <database>.dbo.sysconstraints

Where <database> is the name of a monitored database, for example, "pubs" or "Northwind"By default, everyone has SELECT permissions to the above system tables. DBAs, may have additional permissions available to them.

Setting User Permissions

The DBA can create a new user account for the purpose of database monitoring or use an existing user account. The DBA does not need to assign "Server Roles" and "Database Access" to this account. However, if the DBA has changed the default settings of some databases for security purposes, the DBA must give "SELECT" permissions of that system tables explicit.

Oracle 8i

Follow the instructions in this section to set permissions for the user account on an Oracle 8i Database (Oracle 8i Enterprise Edition Release 8.1.7.0.0).

Object Permissions

At a minimum, the account for database monitoring must have SELECT permissions for the following objects:

• sys.dba_tables

• sys.dba_tab_columns

• sys.dba_constraints

• dba_views

• dba_objects

Note:

sys.dba_procedures is not a requirement.

Setting User Permissions

Typically, a new account does not have any SELECT permissions for the above objects. The DBA must assign the SELECT_CATALOG_ROLE role to this account. The SELECT_CATALOG_ROLE will make available the above objects as well as other objects. You may then manually set each object's permission level for your user. Keep in mind that if the user wishes to perform SQL queries as part of the Configuration Change Console monitoring, the tables listed above will need to be accessible to the user internally configured in your database Configuration Change Console.

After assigning SELECT_CATALOG_ROLE to this account, the agent can use the account to connect to the Oracle 8i server.

Oracle 9i/10g/11g

If you are running an Oracle 9i, 10g, or 11g database, follow the instructions in this section to set permissions for the user account.

Object Permissions

At a minimum, the account for database monitoring must have SELECT permissions for the following objects:

• sys.dba_tables

• sys.dba_tab_columns

• sys.dba_constraints

• sys.dba_views

• sys.dba_objects

• sys.dba_procedures

Setting User Permissions

Typically, a new account does not have any SELECT permissions for the above objects. The DBA must assign the SELECT_CATALOG_ROLE role to this account. The SELECT_CATALOG_ROLE will make available the above objects as well as others. You then have the option to manually set each object's permission level for your user. Keep in mind that if the user wishes to perform SQL queries as part of the Configuration Change Console monitoring, the tables listed above will need to be accessible to the user internally configured in your database Configuration Change Console.

After assigning SELECT_CATALOG_ROLE to this account, the agent can use the account to connect to the Oracle 9i or 10g server.