When the SQL Server Tier is installed, post-installation tasks may be required. This may depend on whether Precise for Storage or ERP Extension is installed.

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 parameter

  1. Open the PeopleSoft configuration file: psappsrv.cfg (usually under PT%version%/appserv/%domainName%). If EnableDBMonitoring=1, proceed to step 6. Otherwise, continue with the next step.
  2. Disconnect all PeopleSoft users.
  3. Shut down all PeopleSoft servers.
  4. Edit the DB Monitoring parameter to be TRUE: EnableDBMonitoring=1
  5. Restart the PeopleSoft application servers.
  6. 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.
  7. 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


IDERA |  Products | Purchase | Support |  Community |  Resources |  About Us  | Legal