Set Up Databases Manually

Owned by Martin Moghadam
Last updated: Nov 27, 2019 by Yüksel Aydemir (Unlicensed)
3 min read

When you install PerformanceGuard, the PerformanceGuard installer offers to automatically create the PerformanceGuard frontend and backend server databases for you. If you want the installer to do this for you, you must provide system administrator (sa) credentials for the SQL Server(s) that'll host the databases.
This is by far the most convenient way to set up the databases. However, many organizations have strict rules that only allow selected people, typically database administrators (dbas), to be in charge of SQL Servers and know the sa credentials for those servers. If that's the case in your organization, you'll not be able to set up the frontend and backend server databases during the PerformanceGuard installation.
In those cases, you—or more likely your dba—can set up the frontend and backend server databases manually after you have installed PerformanceGuard:

Step 1: Create Databases

On the server on which you have installed PerformanceGuard, do the following:
From an elevated command prompt, run a command to create the backend server database. The command should be similar to the one in the example, but you should substitute the PerformanceGuard installation paths and argument values with relevant paths and values for your organization:

Example: "C:\Program Files\Performanceguard\sqlscripts\patchscript\PatchDatabase.exe" -s localhost -u sa -p sa -d pguard -f "C:\Program Files\Performanceguard\sqlscripts\step1_sa.sql" -m install

 What's an elevated command prompt?

It is a command prompt that's able to execute commands with administrative privileges. To get an elevated command prompt, click /Start, type cmd, right-click Command Prompt in the search results, and select Run as administrator.

In doubt about what the arguments (-s, -u, etc.) mean? See the List of Arguments in the following for descriptions.

 
Then run a command like the one in the following example to create the frontend server database. Again you should substitute the example's paths and arguments with relevant paths and values for your organization:

Example: "C:\Program Files\Performanceguard\sqlscripts\patchscript\PatchDatabase.exe" -s localhost -u sa -p sa -d pguardfe -f "C:\Program Files\Performanceguard\sqlscripts\step1_fe_sa.sql" -m install


List of Arguments

  1. -s SERVER: SQL server to use. Example: localhost.
  2. -d NAME: Name of database to patch or create.
  3. -u USER: SQL user to perform actions. For install mode (see the following) a user with authorization to create a new database must be used, for example the sa user.

  4. -p PASSWORD: Password of user.

    Make sure to use a lower case p. The upper case P is used for the properties argument.

  5. -D DIRECTORY: Folder that contains the SQL patch files. Make sure that you use a folder with appropriate SQL files, that is FExxxxx.sql files for frontend server database and BEExxxxx.sql files for backend server databases.
  6. -f FILE \[FILE ...\]: SQL file to apply to database; used instead of --directory to specify a single SQL file.
  7. -m {install,patch}: The mode to run: patch (patching an existing database) or install (create databases with administrator user).

  8. -P PROPERTIES: The name of a file that contains key value pairs. All occurrences of a key in the SQL scripts will be replaced by its corresponding value.

    Make sure to use an upper case P. The lower case p is used for the password argument.


Step 2: Patch Databases

On the server on which you have installed PerformanceGuard, do the following:

From an elevated command prompt, run a command to perform a necessary patching of the backend server database. The command should be similar to the one in the example, but you should substitute the PerformanceGuard installation paths and argument values with relevant paths and values for your organization:

Example: "C:\Program Files\Performanceguard\sqlscripts\patchscript\PatchDatabase.exe" -s localhost -u pguard -p pguard -d pguard -D "C:\Program Files\Performanceguard\sqlscripts\BackEnd" -m patch -P "C:\Program Files\Performanceguard\sqlscripts\sqlproperties_backend.properties"

Can you remember what the arguments (-s, -u, etc.) mean? If not, see the List of Arguments in the previous step.

Then run a command like the one in the following example to patch the frontend server database. Again you should substitute the example's paths and arguments with relevant paths and values for your organization:

Example: "C:\Program Files\Performanceguard\sqlscripts\patchscript\PatchDatabase.exe" -s localhost -u pguardfe -p pguardfe -d pguardfe -D "C:\Program Files\Performanceguard\sqlscripts\FrontEnd" -m patch -P "C:\Program Files\Performanceguard\sqlscripts\sqlproperties_frontend.properties"

Step 3: Start PerformanceGuard Services

When the frontend and backend server databases have been set up, make sure that you start the following PerformanceGuard services:

  • PerformanceGuard Backend Server service
  • PerformanceGuard Frontend Server service
  • PerformanceGuard Web Server service

You can either do this through Windows' Service Manager or from a command line with the following commands:

net start pgbackend
net start pgfrontend
net start pgdisplay





Search this documentation

On this page

In this section