Complete the following steps to automatically create a SQL Server or SQL Server Express database and load application data:
If you will be loading a license key file as part of this procedure, copy the file to hard disk before you begin. A license key file is required to use the software and should have been provided via e-mail or CD. It contains your company name, serial number, the product components with version number you have purchased, and the number of users allowed.
1 If you are installing from a CD, insert CD 1. An introductory screen should appear that provides installation options.
If the screen does not appear, or if you are installing from a network location, double-click autorun.exe in the root folder of CD 1.
2 On the main Primavera screen, choose Install Other Tools.
3 On the Other Tools screen, choose Server Databases.
Click Next on each wizard dialog box to advance to the next step.
4 On the Welcome! dialog box,:
• Choose Create a new Primavera database.
• In the Key field, enter the product key located on the CD 1 label.
5 On the Select Database Type dialog box:
• Choose Microsoft SQL Server/SQL Express as the database type.
• Choose whether to include sample project data in the database.
• If you want to use a currency other than US Dollars as the base currency for the database, select a different base currency in the To change the base currency field.
YOU MUST CHOOSE THE BASE CURRENCY IF YOU DO NOT WANT THE DATABASE TO USE US DOLLARS ($) AS THE BASE CURRENCY. IT IS NOT POSSIBLE TO CHANGE THE BASE CURRENCY ONCE PROJECTS ARE IN
PROGRESS.
Setting the Base Currency
For information on adding view currencies, refer to the
“Defining Administrative Preferences and Categories”
chapter of the Project Management Reference Manual.
The base currency is the monetary unit used to store cost data for all projects in the database and is controlled by a global administrative setting in the Project Management module. The default base currency for Primavera is US dollars ($). The view currency is the monetary unit used to display cost data in Primavera and is controlled by a user preference.
The exchange rate for the base currency is always 1.0. When a user selects a different currency than the base currency to view cost data, the base currency value is multiplied times the current exchange rate for the view currency to calculate the values displayed in cost and price fields.
For example, if the base currency is U.S. Dollars, the view currency is Euros, and the exchange rate for Euros is .75, a value of $10 stored in the database is displayed as 7.5 Euros in cost and price fields. Similarly, if you enter 7.5 Euros in a cost or price field, it is stored in the database as $10.
When data is displayed in a view currency that is different than the base currency, some cost and price values may vary slightly (e.g., due to rounding). As long as the correct base currency is selected during database installation, a user can view completely accurate cost and price data by changing the view currency to match the base currency.
6 On the Select Application database dialog box, choose the database for which you are installing data.
7 On the Select Installation Method dialog box:
• Choose Create Database and Load Application Data.
• Mark Load the license key file.
• Browse to the location of the LICENSE.TXT file. If the
LICENSE.TXT file is not available at this time, you can clear this checkbox and load the file later using the Database wizard. Refer to “Changing Database Configuration Settings” on page 299 for more information.
8 On the Microsoft SQL Server Details dialog box:
• In the System Admin Name field, type the Microsoft SQL Server system administrator name to register to the server. If you chose the defaults during the Microsoft SQL Server installation, accept SA as the system administrator name.
• In the System Admin Password field, type the password for this system administrator. If you chose the defaults during the Microsoft SQL Server installation, accept a blank password.
• In the Server Name field, enter the server machine name or IP address where Microsoft SQL Server is installed. You must specify a server name. If you are running the Database wizard from the server machine, the Database wizard automatically enters the server name for you.
9 On the Configure SQL Server Database dialog box, click Next to accept the default values, or change them as appropriate to your installation.
If change the name of the database, duplicate database names are not permitted—you are prompted to enter a unique name if a database with the specified name already exists.
Do not use a dash (-) in the database name; it will cause errors.
The data file contains the database tables and procedures. The log file contains a record of changes. By default, the Database wizard stores these files in the folder on your server where Microsoft SQL Server is installed. The database name that you specify is used to name the files. If you change the location, the destination folder must exist on the server.
10 On the Ready to Begin Creating Database Structure dialog box, choose YES, I Want to Create Database Tables and Structure.
If the database creation fails before completion, a Database Creation Failed dialog box appears with messages stating the errors. Click Copy to Clipboard on this dialog box to record the messages and contact Customer Support for more information.
11 On the Load Application Data dialog box, click Next to start the process of loading the database tables with application data.
When the process has completed, the message “Data Loading Completed” appears. Click Finish to exit the wizard.
12 Run the Database wizard again if you will be using the Methodology Management module.
Once both sets of application data are installed (project management and methodology management), you can begin to install client modules and additional components. Refer to Part 3 and Part 4 for more information on configuring the servers and installing client module(s) and additional components. For information on configuring database settings to optimize performance, refer to “Database Administration” on page 57.