Page History

...

1. From StartPoint, click the AdminPoint tab.
2. Click the Setup tab.
3. From the drop-down menu, select Instances & Clusters.
4. Click the All instances tree item
5. At the bottom of the Display Instances & Clusters screen, click Add Instance. An Add New Instance dialog box appears.
6. Select the required technology from the list.
7. Select the application from the list.
   If the desired application is not on the list, follow steps a-d:
   1. Click Add.
   2. In the Application Name field, type in the new application name.
   3. On the Application System field, select the system application from the list.

   4. Click OK.

      Info
      To install an instance in an application, you must have ADMINISTRATE.INSTALL permission for the application in which you want to install the instance. If you only have permission for a specific technology, you will only be able to install in an application that is either empty, or is comprised of only the same technology.

8. Select a Tier from the list.

9. Click OK to view the next screen.

   Info
   Always refresh AdminPoint after adding an instance.

...

To define SQL property settings

1. Click the “SQL "SQL Server Instance / <Host>,<Port>” <Host>,<Port>" drop-down menu and select the SQL Server instance.

   Info
   This is the name of the SQL Server instance you want to monitor. The list includes all instances that were detected in the Local Area Network. To monitor a different instance, type the instance name. SQL Server instances that contain the ‘$’ sign are not supported. If you choose a remote SQL Server instance, you will see the remote host server in the Servers list.

   Info
   You can also insert an instance using the format "<host>,<port>", where <host> <host>,<port>," where <host> is the server name and <port> <port> is the port of the SQL server instance. This is useful when the SQL Server browser service is disabled or deactivated.

2. Click the “Monitor "Monitor SQL Server activity from this server” server" drop-down menu and select the server from the list. Click Add to enter the name of a server not on the list. For more information, see Adding a new server on page 44.

   Info
   This is the server where you want to install the SQL Server Tier Collector. The server name or IP address appears in the list only if you previously defined it as a Precise server. You can install the Collector either on the sampled server, or on a remote server. If you wish to associate the Collector with Precise for Storage, you must install the Collector on the sampled server.

   Info
   When you want to delete the server, you will have to delete the dependent instances first before you are allowed to remove this server.

3. Click the “Connect using” "Connect using" drop-down menu and select the authentication type for the SQL Server.

   Info

   This is the authentication type the SQL Server Tier Collector will use to log in to the SQL Server instance. Select Windows Authentication to log in with the Windows user used to start the Precise for SQL Server service. Select SQL Server Authentication to log in with an existing SQL Server login name. To use Windows Authentication, you may need to change the user with which you log in to the Precise for SQL Server services (this means that this user needs to become the user who is defined in the SQL instance and has the Administrator permissions). If the Collector is installed on the monitored server, open the Services window and change the user with which you log in to the Precise for SQL Server Collector and the Precise Listener agent service. If the Collector is installed on a different server than the monitored instance, see step 6 below. When installing the Listener agent, you can choose to install all services with a dedicated Log In user.

4. Enter your Login name.

   Info
   If you connect using Windows Authentication, the login is based on the login used to start the Precise for SQL Server agents. If you choose SQL Server Authentication, an existing SQL Server user name and password with system administrator privileges are required here.

5. Enter the password.

6. If the PMDB is using Windows Authentication, or the Collector is using remote sampling, at the bottom of the screen, under "Use different Windows Service credentials than the LocalSystem account," enter accounts with the following permissions:
   Table 18-1 Permissions

   When	Permission	Where
   Remote sampling	User with full control permission	On the Precise folder
   	User who is allowed to use Windows Authentication User with full control permission	On the PMDB server On the Precise folder
   Remote sampling and PMDB using Windows Authentication	User who is allowed to use Windows Authentication User with full control permission	On the PMDB server On the Precise folder
   PMDB uses Windows Authentication and associating to Precise for Storage	System Administrator	On the monitored server

   To add the parameters

   1. On the Windows Authentication Settings screen, enter the user name.
   2. Enter the Password.
   3. Enter the Domain or Server name.
7. Click Next.

...

After you install SQL Server, a user who is a member of the sysadmin fixed server role must launch Database Engine Tuning Advisor before anyone else. When the sysadmin user launches Database Engine Tuning Advisor that action initializes the application for use by others. After Database Engine Tuning Advisor is initialized, any user who is a member of the db_owner fixed database role can use it to tune tables on databases they own. For more information about initializing Database Engine Tuning Advisor, see the Initializing Database Engine Tuning Advisor on the MSDN website.

Installing the product Interpoint for PeopleSoft Collector trigger

If you have installed the Interpoint Collector to monitor PeopleSoft activities, you need to create a trigger on the table PSPRCSRQST in the PeopleSoft database. In addition, you need to enable the database monitoring parameter in the PeopleSoft configuration file.

To install the Interpoint for PeopleSoft Collector’s trigger and enable the database monitoring parameter1.    Open

1. Open the PeopleSoft configuration file: psappsrv.cfg (usually under PT%version%/appserv/%domainName%). If EnableDBMonitoring=1, proceed to step 6. Otherwise, proceed to step 2.

...

1. Disconnect all PeopleSoft users.

...

1. Shut down all PeopleSoft servers.

...

1. Edit the DB Monitoring parameter to be TRUE:  EnableDBMonitoring=1

...

1. Restart the PeopleSoft application servers.

...

1. Using SQL Query Analyzer, connect to the database holding the PeopleSoft tables. Verify that you are connecting with a user that is a member of the db_owner database role in the database.

...

1. Execute the following batch:
             if exists (select name from sysobjects where name = 'precise_psprcsrqst_register' and type = 'TR')
             drop trigger precise_psprcsrqst_register go
             if exists (select name from sysobjects where name = 'VERITAS_psprcsrqst_register' and type = 'TR')
             drop trigger VERITAS_psprcsrqst_register go
             if exists (select name from sysobjects where name = 'Symantec_psprcsrqst_register' and type = 'TR')
             drop trigger Symantec_psprcsrqst_register go
             create trigger precise_psprcsrqst_register on PSPRCSRQST for update as
        declare @oprid char(30), @prcsinstance int, @old_status int, @new_status int, @info binary(50)
        select @old_status = RUNSTATUS from deleted select @new_status = RUNSTATUS from inserted if (@new_status <> 7) or (@old_status = 7) return
        select @oprid = OPRID, @prcsinstance = PRCSINSTANCE from inserted
        set @info = convert(binary(50), rtrim(@oprid) + ',' + convert(varchar(20), @prcsinstance))
        set context_info @info go

Precise. Performance intelligence from click to storage. Learn more > >