SEER-HD Database Administrator s Guide

SEER-HD Database Administrator s Guide Rev. April 30, 2010-1 -

Contents Introduction... 3 How SEER-HD Works... 4 Interaction of SEER-HD with Other SEER Programs... 5 Database Platforms... 6 Getting Started... 6 SEER-HD Database Setup Utilities... 6 Two Installers... 6 End User Database Configuration Installer... 7 Local or Server Options... 7 Local Microsoft Access... 8 Server Microsoft Access... 8 Server SQL Server...10 Create Data Source Name (DSN)...12 Check Install Settings...14 Silent Installation - End User Database Installer...15 Record Mode...15 Silent Mode...15 Possible Silent Mode Errors (examples)...16 Manual Installation of Microsoft Access Databases...18 Setting the Default SEER-HD DSN... 20 Setting the registry directly:...20 Setting the Default DSN from within a SEER-HD application:...21 SEER-HD Version Upgrade...21 The RDBUpgrader.exe Application...21 Uninstall/Reinstall...23 SQL Server SEER-HD Installer...25 DBMS...25 Basic Steps... 26 For New SEER-HD Installation...26 Using the SEER-HD SQL Server Database Set-Up Utility...26 1. Create New Database...27 2. Upgrade Existing Database...32 3. Set Default SEER-HD Database...33 Configuring ODBC Data Sources Manually...35 Creating an SQL Server SEER-HD DSN with the ODBC Manager...37 DSN dialog sequence... 37 Create a System SQL Server data source...37 Select the SQL Server ODBC driver...38 Enter a Data Source Name and select the Database Server...39 Authentication Mode...39 Select the Database...40 Further Options...40 Validate Database...41 Access Control...42 Network and Database Server Access... 42 DBMS Access... 42 SQL Server and SQL Server Express...42 Database Access... 44 SQL Server and SQL Sever Express...44 Database Backups...49 Database Transactions and Rollbacks... 49 Data Recovery...49 General Data Corruption... 49 Incomplete Project Revision Data... 49 Removing SQL Server Express Instances...49-2 -

Introduction This guide covers the installation and maintenance of the SEER Historical Databases (SEER-HD), previously known as SEER Repository Databases ( SEER-RDB ). SEER Historical Database (SEER-HD) is a relational database that stores project information used by a variety of SEER applications for estimating such things as size, schedule, and effort. The project information may come from an organization's own record of previous development projects, or it may be reference information from another source. Some SEER applications, such as Estimate by Comparison or Microsoft Project Integration, base their estimates on user-made comparisons between items from SEER-HD and the current project. SEER-Metrics plots project data from SEER-HD on a chart, allowing the user to visually compare historical/reference data to the current project. Other applications and features, such as SEER-Critical Mass, and Analogy-Based Sizing and Analogy-Based Estimating in SEER-SEM, automatically estimate size based on the user's SEER- HD selections and choice of estimating options. The SEER-HD database is available in two formats, Microsoft Access and SQL Server. SEER-HD data is managed by the SEER Historical Database Administrator (SEER-HDA), which can add, delete, and configure project data in a SEER-HD database (SEER-HDA was previously known as SEER-RAA, - 3 -

SEER Repository Administrator). For information about using SEER-HDA, consult your SEER-HDA user s documentation or HTML help. How SEER-HD Works All SEER-HD-enabled SEER applications look in the SEER-RDB registry key for the name of the current SEER-HD DSN. (The key SEER-RDB is a holdover from SEER-HD s previous incarnation as SEER-RDB.) The SEER-RDB key is: Key Variable Value HKEY_LOCAL_MACHINE\SOFTWARE\Galorath\SEER-RDB DSN SEER-HD After retrieving the DSN value, programs then look for a System (machine-wide) DSN with the same name to query for data: - 4 -

Interaction of SEER-HD with Other SEER Programs You may have more than one SEER-HD database Data Source Name (DSN) on your machine if you wish to segregate comparison data. However, only one of these at a time may be your active (default) repository. SEER programs that use SEER-HD are normally able to set (i.e., change) the SEER-HD default data source. When you change data sources in one SEER application, you are effectively changing it for ALL other SEER applications, since the new data source name is written to the shared SEER-HD DSN registry key. Specify Repository option in Microsoft Project Integration NOTE: The current generation of SEER-HD-enabled SEER programs (Microsoft Project Integration, Estimate by Comparison, and SEER Metrics) do not support SQL Server database authentication. Hence ODBC database access for SQL Server databases should be configured as Windows authentication. Although SEER-HDA will support SQL Server authentication, all other SEER-HD-enabled programs use the same registry DSN key to locate the database. Hence even though setting SQL Server authentication will work for SEER-HDA, it will fail when you attempt to run other SEER-HD programs. Hence always set Windows authentication. - 5 -

Database Platforms SEER-HD 2.0.0.3 and above databases are currently supported in Microsoft Access database file (*.mdb) format and as Microsoft SQL Server databases hosted on SQL Server (2000 and above) and SQL Express 2005 and above. Microsoft Access file database do not require the presence of Microsoft Access on your computer. In order to install SQL versions of the database, you must already have installed Microsoft SQL Server (2000 or above) or SQL Express 2005 or above on your computer. SQL Express 2005 is a free download available from Microsoft s download web site. Both types of SEER-HD (SQL 2000 or 2005) database require the use of Microsoft Windows. Prior to version 2.0.0.0, SEER-HD used to be known as SEER-RDB (for SEER Repository Database) and could be installed on Microsoft s MSDE desktop SQL server. SQL Express 2005 has been substituted for MSDE, however, since it is better supported on Microsoft s new Vista operating system. Databases that have already been installed on MSDE can be updated by current SEER-HD database installers. If you need more information about MSDE, please contact Galorath Incorporated. General The software design of SEER applications allows an instance of the SEER-HD database to be hosted by any ANSI-SQL-compliant relational database management system (RDBMS) which has an ODBC driver available for the target operating system. In other words, theoretically, a SEER-HD database could be exported and converted to any other ANSI-SQL compliant database type. Getting Started SEER-HD Database Setup Utilities Two Installers There are TWO SEER-HD Setup programs: (1) a Default installer for installing a Microsoft Access SEER-HD database and (2) an SQL Server installer for installing a SEER-HD database on SQL Server (2000 and 2005) or SQL Express 2005. The installers also allow users to create an ODBC connection with any already installed SEER-HD database. SEER-HD Microsoft Access Default Installer (Installs an MS Access Database) SEER-HD SQL Server Installer (Installs SQL Server databases) - 6 -

End User Database Configuration Installer The Default SEER-HD installer is located in the SEER-HD directory of your SEER software installation CD. It is run by clicking on the setup.exe file or by launching setup.exe from the DOS command line. It may also be automatically launched by other SEER application installers if it has not yet been installed. A few important things are necessary to know about the Default Microsoft Access SEER-HD installer that comes with your programs. 1. This install package will enable you to connect to a SEER-HD (either MS Access or SQL Server) installed on an enterprise server. 2. This installer will optionally set up a local SEER-HD Microsoft Access database. 3. If you already have a local Microsoft Access SEER-HD database installed, this installer will upgrade it to the latest version. Any previous databases will be backed up. 4. This installer will NOT install or upgrade SQL Server SEER-HD databases. For that you need the SQL Server installer. This installer will also NOT upgrade any database that is located on a network server, since that is the duty of your system administrator. Local or Server Options When the installer runs, it enables the user to do one of the following: Install or upgrade a Local copy of a Microsoft Access SEER-HD database. (Local option) Create a DSN for an already installed Remote instance of Microsoft Access SEER-HD or SQL Server SEER-HD database. (Server option) Note: If you already have an existing Local SEER-HD database of the SAME version as the installer, you will not be able to proceed to the install directory dialog. The installer will inform you that your database is already up-to-date and allow you to switch database types if you desire. (See Uninstall/Reinstall below if you wish to reinstall a same version database.) - 7 -

Local Microsoft Access Install Directory You may install a Microsoft Access SEER-RDB.MDB database file wherever you wish on the Local machine, but the directory needs to be writable by all users who will access the database. Directory Privileges -- Important! In order to function properly for ALL users on a machine, including those who have Restricted User Profiles, the database should be installed in a directory to which ALL users have read and write access. The default All Users profile directory satisfies this condition on most computers. If you change the default, note that the installing user normally has administrative privileges to access any directory on the Local Machine, but not every user does. Be careful that you choose a directory that is accessible by ALL users who plan to use SEER-HD-enabled applications, or that you plan to MAKE the directory accessible to everyone after installation. If you are installing on Vista, the default installation directory is C:\ProgramData\SEER\SEER-RDB. The installer will give your database file Users group privileges. However, you may also install the database in any location where restricted users have write privileges. Server Microsoft Access The Default SEER-HD installer will allow you to select a SEER-HD Microsoft Access database located on a remote server if you select the Server option followed by Microsoft Access database type: - 8 -

Users are then given the option of selecting a Microsoft Access (.MDB) database file on a remote computer. This database must have already been installed on the server by a systems administrator. Systems administrators should take care that the database is 1. the appropriate version or upgraded to the appropriate version, 2. not password protected (Microsoft Access password protection is not supported), 3. in a directory readable and by all users who plan to install SEER-HD, 4. in a directory that is writable for any users who plan to update data in the database. The installer tests that 1. the database is on a remote machine, - 9 -

2. the database is a SEER-HD database, 3. the database is NOT password protected (in order to determine the database version, the installer must be able to access it), 4. the database is the same version or higher than the installer specifies (if you have a version 2.0.0.0 installer, it will expect you to select a version 2.0.0.0 database or higher). In the fourth case, the installer will warn if the database is out-of-date, but it will not prevent the user from creating a DSN. It is up to systems administrators to make sure that Server SEER-HD databases are updated before users attempt to establish connections to them. Server SQL Server See Create Data Source Name (DSN) below for the final step in creating a Microsoft Access SEER-HD DSN. Two extra steps are required before creating a DSN for SQL Server databases: (1) logging on to the SQL Server instance where the database is located, and (2) selecting the database name. SQL Server Instance SQL Server Instance Name: The drop-down box lists all servers available to the user on the NETWORK. (local) instances, however, are not represented with complete names. For a local server instance, you must complete the Instance name yourself. For example, if you installed SQL Express as SQLEXPRESS, you need to complete the (local) selection by adding the instance name with a backward slash before it: SQLDEV1 (network server name) - 10 -

(local)\sqlexpress (completed local server name) Log On Note: Previous SEER-RDB installers allowed users to install SEER-HD databases using Microsoft s MSDE desktop version of SQL Server. As of SEER-HD 2.0.0.3, MSDE is no longer supported as a local database server. SQL Server Express 2005 is substituted in order to support the Microsoft Vista operating system. SQL Express 2005 needs to be installed separately. It can be obtained as a free download from the Microsoft web site. The current generation of SEER-HD-enabled programs (Microsoft Project Integration, Estimate by Comparison, and SEER Metrics) support Windows user and password authentication only. Administrators should see "Network and Database Server Access" below for instructions on manually setting user names and passwords on SQL Server or SQL Express databases. Connect with Windows authentication using the network login ID If you select this option, the SQL Server Login ID and Password text boxes will be grayed out. If you select a remote SQL Server, your SQL Server administrator must have granted login privileges for your Windows login ID to access the SQL Server. If you are installing a fresh local SEER-HD database on SQL Server Express, you will need to set Windows access for specific users from within the SQL Express Management console. Note: If you have previously installed SEER-RDB database installed on a local instance of MSDE, you should automatically have Windows Authentication access to the SQL Server instance if you log on to your computer with Administrators privileges. Connect with SQL Server authentication using a login ID and password The current generation of SEER-HD-enabled SEER programs does not support SQL Server user and password authentication. You should set Windows Authentication. - 11 -

SQL Server Database Enter the SQL Server database where SEER-HD data is stored. The default name for a new database is SEER-HD. SQL Server database name Databases are not automatically listed in the drop-down box. You need to get the database name from your SQL Server administrator or know it from having installed a local SQL Express Server instance and having created the database yourself. See Creating an SQL Server Database below for instructions on creating an SQL Server database using the SQL Server SEER-HD setup utility. Create Data Source Name (DSN) All Microsoft Access or SQL Server SEER-HD database scenarios require you to create a data source name for the database to which you are connecting. - 12 -

System DSN name The ODBC data source name by which programs will connect to the SEER-HD database. The default DSN name is SEER-HD. You may change that if: There is no existing SEER-HD DSN, your selection will be set as the default SEER-HD DSN. If a DSN with the same name already exists, you will be asked if you wish to replace the existing DSN. Some users may wish to maintain more than one SEER-HD DSN -- for example, a local Microsoft Access SEER-HD and a server SQL Server SEER-HD. You may do this by simply naming the DSNs differently. If a SEER-HD with a different name already exists, you will be asked if you wish to set your new DSN as your default SEER-HD DSN. In either case the DSN will be created. But if you choose YES, the new DSN will be written to the SEER-RDB DSN registry key that is used by other SEER programs to access your database. In other words, the new DSN will be used by other SEER applications as your new SEER Historical Database. DSN description DSN description is an optional field for giving a description to your DSN so that you know what it is for. SEER Historical Database is the default description. Check DSNs - 13 -

The Check DSNs button is for checking the names of your SEER-HD database(s). You can also rename an old DSN if you want to reuse its name for the DSN that you are creating. You can also delete DSNs. However, beware that the replacement data you see in the Start Copy dialog will not be correct if you delete the currently existing SEER-HD database. If you wish to delete DSNs, it is better to do so BEFORE running the installer. Check Install Settings The final dialog of the SEER-HD installer presents you with a summary of the information gathered and actions to be taken by the installer. Review this information before pressing the next button. You may actually copy out this data by highlighting the text and using the Windows Ctrl + C keyboard command to copy information to the clipboard, and then paste it elsewhere using Ctrl + V. Data collected and what it means: NEW DATA SOURCE (header at the top of the screen): The data source that will be created by the installer session. EXISTING DATA SOURCE (header at the bottom of the screen): The existing data source discovered by the installer on startup. If no existing database was found, there will be no EXISTING DATA SOURCE section. SetupType: Server or Local Database Type: SQL Server or MS Access Install Path (DBQ): The fully qualified path where the Microsoft Access database will be installed. Applies only when you are installing or updating a local Microsoft Access database. For example: C:\Documents and Settings\All Users\Application Data\SEER\SEER-RDB\SEER-RDB.mdb. (The SEER-RDB designations are preserved for compatibility with older SEER-HD databases.) Server Database Path (DBQ): The fully qualified path to a Microsoft Access database on a remote server. Applies only to Microsoft Access and only to server DSNs. For example: Q:\seer-rdb\SEER-RDB.mdb. (The SEER-RDB designations are preserved for compatibility with older SEER-HD databases.) Server: The SQL Server instance name to which you are connecting. Applies only to SQL Server DSNs. Database: The name of the SQL Server database on the SQL Server instance to which you are connecting. Applies only to SQL Server DSNs. Normally this might be named SEER-HD, but it could actually be any name created by your systems administrator. Data Source Name (DSN): The name of the DSN as it will appear in the ODBC Manager s System DSN tab. - 14 -

DSN Mode: Either CREATE a new DSN or REPLACE an existing DSN. If you already have a DSN of the same name that you have selected for the DSN for your current installation, the installer will replace the existing DSN. This can be disadvantageous if you are switching from one type (MS Access) to another (SQL Server) and want to maintain a DSN for each on your computer, or if you otherwise want to install multiple SEER-HD databases. REPLACE, as the name would suggest, makes all information about your existing SEER-HD DSN disappear. Silent Installation - End User Database Installer The preferred mode is to have users run the End User Database installer with full visible GUI so that they can change options if the installer discovers issues with their current configuration. However, we realize that systems administrators often wish to push applications out to their users using silent installation. Hence the end user database installer allows a limited range of silent installation options, although administrators need to be careful of the limitations and pitfalls of running the installer in silent mode. In order to run silent mode one must first record a silent install script by running the installer in RECORD MODE. Record mode saves one s choices to an *.ISS file that the installer plays back during the silent installation process. Record Mode To generate an *.ISS recording, run the installer from the command line with the /r and /f1 flags. We suggest outputting the file to C:\setup.iss, since the default output location (the Windows directory) is a little inconvenient. Also, if you wish to avoid having to specify the.iss file name on the silent installation command line, we suggest that you use setup.iss, the default. "<full path to setup.exe>\setup.exe" /r /f1"c:\setup.iss" If you wish, you may add logging to the command line. The /v flag passes commands to the installer s.msi file. Internal quotes need to be escaped with a backward slash: /v"/l*v \"c:\rdblog1.log\"" For further explanation of installer setup.exe and MSI command line options, see command line help at the Flexera web site knowledge base: http://kb.flexerasoftware.com/doc/helpnet/installshield12helplib/ihelpsetup_execmdline.htm Silent Mode Copy the setup.iss file you created to the installer s directory and run the installer with the silent /s flag. We suggest that you add MSI logging to the command line in case anything goes wrong with the silent setup: "<full path to setup.exe>\setup.exe" /s /v"/l*v \"c:\rdblog2.log\"" It is NOT necessary to specify the setup.iss file on the command line if you have named the file setup.iss and have placed it in the installer s root folder. However, if you have changed the defaults, you will need to add the /f1 flag to your silent installation to tell the installer where to find the silent script: "<full path to setup.exe>\setup.exe" /s /v"/l*v \"c:\rdblog2.log\"" /f1"c:\setup.iss" - 15 -

The setup.exe will generate an automatic setup.log file in the installer directory (or you can use the /f2 flag to redirect the location and name of that log file). The setup.log, however, contains only setup.exe results. Result = 0, for example, means the installer completed and exited successfully. http://kb.flexerasoftware.com/doc/helpnet/installshield12helplib/setuplog.htm To detect any SEER-HD-specific errors, inspect the end of the C:\rdblog2.log.MSI log that you have specified with the verbose MSI logging command you passed to the MSI installation process: Possible Silent Mode Errors (examples) Example One Remember that the installer does not automatically remove the database and its DSN when the installer is uninstalled. This is by design, since we do not wish to automatically delete data that users have entered into their historical databases. If your user has run uninstall from the Add/Remove control panel, they will still have a SEER-HD database setup. If you then rerun the installer silently with the following first-time SEER-HD Microsoft Access installation script, it will discover the existing setup and exit before it even gets to the SetupType dialog (line 4). Setup.iss This setup.iss is configured for a first-time installation of a SEER-HD Microsoft Access database. [{9DD389CB-06C7-4674-A8B9-361AB2294942}-DlgOrder] Dlg0={9DD389CB-06C7-4674-A8B9-361AB2294942}-SdWelcome-0 Count=6 Dlg1={9DD389CB-06C7-4674-A8B9-361AB2294942}-SetupType2-0 Dlg2={9DD389CB-06C7-4674-A8B9-361AB2294942}-SdAskDestPath-0 Dlg3={9DD389CB-06C7-4674-A8B9-361AB2294942}-DsnSetup-0 Dlg4={9DD389CB-06C7-4674-A8B9-361AB2294942}-SdStartCopy-0 Dlg5={9DD389CB-06C7-4674-A8B9-361AB2294942}-SdFinish-0 [{9DD389CB-06C7-4674-A8B9-361AB2294942}-SdWelcome-0] Result=1 [{9DD389CB-06C7-4674-A8B9-361AB2294942}-SetupType2-0] Result=304 [{9DD389CB-06C7-4674-A8B9-361AB2294942}-SdAskDestPath-0] szdir=c:\documents and Settings\All Users\Application Data\SEER\SEER-RDB\ Result=1 [{9DD389CB-06C7-4674-A8B9-361AB2294942}-DsnSetup-0] ndsnflag=-1001 g_szdsn=seer-hd g_szdatasourcedesc=seer Historical Database Result=1 [{9DD389CB-06C7-4674-A8B9-361AB2294942}-SdStartCopy-0] Result=1 [{9DD389CB-06C7-4674-A8B9-361AB2294942}-SdFinish-0] Result=1 bopt1=0 bopt2=0 rdblog2.log Note that the installer explains that it is exiting because it has found an existing installation of SEER-HD of the same version. - 16 -

MSI (c) (D0:FC) [16:03:48:943]: PROPERTY CHANGE: Adding SETUPTYPE property. Its value is 'Local'. 1: You already have a Local installation of Microsoft Access SEER Historical Database 2.0.1.4. Silent installation will now cancel you out of the installer. === Verbose logging stopped: 4/27/2010 18:22:31 === In order to have avoided the installer exiting rather than installing a fresh copy of the SEER-HD MS Access database, your user would have had to delete or rename their existing SEER-HD DSN, and they would have had to delete, move or rename the SEER-RDB.mdb database in their SEER-HD folder (C:\Documents and Settings\All Users\Application Data\SEER\SEER-RDB\ ) before running the silent installation. Example Two (MS Access database upgrade) The existing installation of SEER-HD has NOT been uninstalled from Add/Remove. A newer version of the installer recognizes that it needs to go into UPGRADE mode to update the database to a newer version. But it discovers that the SEER-HD DSN points to a REMOTE MS Access SEER-HD database on a server. The installer is not allowed to upgrade remote databases, since that is the responsibility of the system administrator. So it exits. Setup.iss This setup.iss presumes that the user has a LOCAL installation of MS Access SEER-HD and runs in upgrade mode, which tries to update the database using the RDBUpgrader.exe. Note that the silent script references only two Message boxes, to which the response is YES (1). [{9DD389CB-06C7-4674-A8B9-361AB2294942}-DlgOrder] Dlg0={9DD389CB-06C7-4674-A8B9-361AB2294942}-SdWelcome-0 Count=2 Dlg1={9DD389CB-06C7-4674-A8B9-361AB2294942}-MessageBox-0 [{9DD389CB-06C7-4674-A8B9-361AB2294942}-SdWelcome-0] Result=1 [{9DD389CB-06C7-4674-A8B9-361AB2294942}-MessageBox-0] Result=1 Rdblog2.log 1: You have a remote Server installation of the Microsoft Access SEER Historical Database. This database MAY need to be updated by your Systems Administrator. === Verbose logging stopped: 4/27/2010 16:53:41 === - 17 -

Example Three You believe that your user has an existing installation of SEER-H and you want to update it with Galorath s latest SEER- HD installer, so you run the upgrade setup.iss in Example Two. But it turns out that a user in fact has no currently installed installation of SEER-HD. There is no record of SEER-HD in the Add/Remove control panel. Your MSI RDBlog2.log file tells you nothing, but the database did not get installed. Setup.log in the installer directory, however, indicates (ResultCode = -3) that it could not find values that it needed in the *.ISS file. That is because the installer was running as a first time installation and needed the more complete firsttime setup.iss shown in example one. In other words, you cannot run an upgrade *.iss file with a first time installation. If the user has no existing installation, the installer will simply exit for lack of sufficient information. Setup.log [ResponseResult] ResultCode=-3 Manual Installation of Microsoft Access Databases A copy of the Microsoft Access SEER-RDB.MDB database is distributed in the SEER-HD directory of your SEER software CD. You may install it manually, as you can any other Microsoft Access database, by placing it on the computer and establishing a database connection with your ODBC administrator application. 1. Copy the SEER-RDB.MDB database from your installation CD to a directory that is accessible by all users who will be using it. If you are installing a Server instance of Microsoft Access SEER-HD, the location will obviously be on a remote Server. 2. Select the Add button on the System DSN tab of your ODBC Administrator. The ODBC Administrator shortcut is normally accessible through your Control Panel in the Administrative Tools subdirectory (the application itself is odbcad32.exe in your Windows System32 directory): - 18 -

User DSNs You may also create User DSNs for SEER-HD, but these must be created while you are within the specific user profile for which you are configuring the DSN. And since only one DSN name may be the default SEER-HD DSN at any given time for all SEER-HD programs on a specific computer, the same User DSN name must be created in each user profile to guarantee that all users have access to the common SEER-HD database. Also be aware that if one of multiple users changes the DSN using Options/Select Repository to a User DSN that is NOT available to other users, SEER-HD programs will cease to operate for those other users. Hence if you have multiple users of SEER-HD programs on the same computer, it is better to set System DSNs, since these are accessible by everyone on the machine. And generally, it is easier to use System DSNs. 3. Select the Microsoft Access database driver -- Microsoft Access Driver (*.mdb) : 4. Enter a data source name and description and use the Select button to locate the database. 5. Navigate to the database folder and select the database: - 19 -

6. Do NOT set Read Only or Exclusive or any other advanced database options. Setting the Default SEER-HD DSN The final and CRITICAL step is to set the Default SEER-HD DSN in the computer s Registry. You may do this either by directly editing the registry or by selecting the DSN from within an installed SEER-HD application. Setting the registry directly: A. Invoke the Windows Registry Editor by typing regedit in the Run dialog accessible from your Start Menu and press the OK button B. Under the HKEY_LOCAL_MACHINE\SOFTWARE\Galorath key create a SEER-RDB key (if one is not already there) and a string variable named DSN. Use the right mouse button to raise the variable creation menu in the right portion of the Registry Editor dialog. - 20 -

C. Then assign the DSN value that you created in steps 2 through 6. Double-click on the DSN variable to raise the value dialog: Setting the Default DSN from within a SEER-HD application: You may also reset the default SEER-HD DSN by using the Options/Select Repository menu option of any SEER program that uses SEER-HD -- for example, Estimate by Comparison -- but only if you already have an existing operational SEER-HD DSN entry. If a SEER-HD program does not run because it does not have a valid SEER-HD DSN, you can either edit the SEER-RDB DSN key to give it a valid DSN or rerun a SEER-HD installer to reset the registry. SEER-HD Version Upgrade When the installer upgrades a Local Microsoft Access database from a lower to a higher SEER-HD version, it backs up the previous database, installs a new database, then attempts to transfer data from the old to the new database. There are many circumstances which might make data transfer impossible to implement. If you get a message that an installer was unable to transfer data, and you want to preserve your existing data, you will need to run the RDBUpgrader utility to transfer data from the older backup SEER-HD database to the newly installer higher version SEER-HD database. The RDBUpgrader.exe Application The SEER-HD Upgrader application (RDBUpgrader.exe) enables you to transfer data from one SEER Historical Database to another. ( SEER-RDB and RDB designations are holdovers from SEER-HD s previous existence as SEER-RDB.) A shortcut to the RDBUpgrader.exe is available in the SEER/SEER for Software/SEER Historical Database subfolder of your Program Start Menu: The application itself is always installed in your <Program Files>\SEER\SEER-RDB folder. The application consists of two files: RDBUpgrader.exe (the executable) and RDBUpgrader.mdb (an MS Access configuration file that must exist in the same folder as RDBUpgrader.exe ): - 21 -

Copies of RDBUpgrader.exe and RDBUpgrader.mdb can also be found in the SEER-HD folder of your installation CD. User Interface The RDBUpgrader user interface is fairly simple, allowing you to transfer SEER-HD data between either database files (Microsoft Access) or between ODBC data sources (either Microsoft Access or SQL Server DSNs) or any combination of the two (DSNs or files): There are two basic types of data transfer currently enabled: 1. Transfer of data from earlier versions of the SEER_SW_Repository database format shipped with earlier version of SEER-SEM Client (before version 1.4.14 ) and SEER-AccuScope (before version 2.1.2.0). 2. Transfer of data from SEER-HD to SEER-HD databases. The RDBUpgrader warns you of the data transfer that you are about to make so that you have the opportunity to cancel the operation: Command Line The RDBUpgrader can be run from the command line with a limited number of switches. Examples of usage: RDBUpgrader /Items /Silent SourcePath RDBUpgrader /Items /Silent SourceDSN RDBUpgrader /? TargetPath TargetDSN - 22 -

Source path and TargetPath must be fully qualified paths to a Microsoft Access SEER-HD database file and MUST be quoted. SourceDSN and TargetDSN must be DSN names. The whole DSN command must be quoted for example, DSN=SEER-HD Newer in order to accommodate spaces in DSN names. DSNs and File paths may be mixed on the command line. The DSN parameters may be extended with attributes separated by semicolons to make them full DSN connection strings. For example, to add username and password, use the following. "DSN=SEER-HD Newer;UID=MyLoginName;PWD=MyPassword" See your operating system ODBC reference for Microsoft Access (.mdb) and SQL Server database drivers; each type of ODBC database driver supports its own set of connection string attributes Example command line: C:\Program Files\SEER\SEER-RDB>rdbupgrader /Items C:\Documents and Settings\All Users\Application Data\SEER\Common\dbbackup_local\SEER_SW_Repository.mdb SEER-HD Command line switches: /Items Transfers data from earlier Items repository (SEER_SW_Repository) database to the newer SEER-HD database. /Silent Suppresses the Upgrader s graphical user interface. /? Provides command line usage information. Silent switch error codes: 0 - Execution without errors 1 - Incorrect or missing command line parameters 2 - Incorrect command line usage 3 - Source database not found 4 - Target database not found 5 - AddFromSEERRDB.DLL not registered 6 - Error during transfer 7 - RDBUpgrader.mdb is not available 8 - Database versions are not compatible In order to capture /Silent switch error codes, you need to run the RDBUpgrader from other program code that can check the Windows LastError() queue. Uninstall/Reinstall Uninstall may be performed from the Add/Remove Applet of your operating system: - 23 -

Remember that uninstalling does NOT remove the database or any DSNs. It uninstalls the installers memory of what is installed. If you wish to reinstall a clean copy of the local database of the same version, you must do the following. These measures are required because the installer does not actually uninstall your database. 1. Uninstall the SEER-HD installer. This will remove the installer s registry record of its previously having run. 2. Back up your existing database by hand if you do not wish its data to be overwritten. Obviously do not place it where you plan to install the new database or leave it in the default directory if you plan to reinstall there. 3. DELETE RENAME it if you wish the existing SEER-HD DSN using your ODBC Administrator (available through the Control Panel) or to preserve it, so that it no longer corresponds to the name of the registered database. Delete DSN - 24 -

Rename DSN SQL Server SEER-HD Installer The SQL Server SEER-HD Installer is located in an SEER-HD SQL Installer subfolder of the SEER-HD installer on your SEER software CD. It is run by clicking on the setup.exe file or by launching setup.exe from the DOS command line. DBMS To set up a SEER-HD SQL Server database, the host machine for the database must have an instance of one of the following database management programs installed. SQL Server 2000 or 2005. The user is responsible for installing SQL Server prior to running the SEER- HD SQL Server Database Set-Up Utility. SQL Express 2005 for Microsoft Vista support. - 25 -

Earlier versions of the SEER-RDB were supported on Microsoft s MSDE (Microsoft Desktop Engine) SQL database server. That option has been deleted in favor of users installing SQL Express as a local server, since it is better supported on the Microsoft Vista operating system. However, if you have MSDE installed from a previous installation of SEER-RDB, your SEER-HD installer will upgrade MSDE databases if they already exist. Basic Steps For New SEER-HD Installation There are four basic steps in setting up an SQL Server SEER-HD database: 1. Create an instance of the SEER-HD Database. 2. Create DBMS login(s). 3. Create/assign database user(s) for the new SEER-HD database. 4. Configure a default SEER-HD ODBC data source on each user s machine that points to the new SEER-HD database. The first three steps are required before a user can access an SQL Server SEER-HD database from SEER programs. The last step, setting the default SEER-HD database, can be performed from inside of SEER- HD- enabled SEER programs. But it is recommended that you set the default with the SEER-HD installer to save users the extra effort, or possible confusion about which SEER-HD database you may wish them to use. Required Administrative Privileges To create an SQL Server instance of a SEER-HD database, the user must have DBMS administrative privileges for the target instance of the SQL Server DBMS where the database is to be created. The SEER- HD SQL Server Database Set-Up Utility assumes the user has the appropriate SQL Server administrative privileges. If necessary, see Access Privileges below for instructions on setting privileges using SQL Server or SQL Express. For SQL Server and SQL Express For SQL Server and SQL Express, a user will have the required administrative privileges to create a database, if one of the following conditions is satisfied. The user has access to the SQL Server built-in administrator login, sa, for the target instance of SQL Server (2000 or 2005) or SQL Express 2005. The user has access to an SQL Server login with privileges to create a database, on the target instance of SQL Server (2000 or 2005) or SQL Express 2005. The user is a member of the Windows built-in administrators group, Administrators, on the machine where the target instance of SQL Server (2000 or 2005) or SQL Express 2005 is located. Using the SEER-HD SQL Server Database Set-Up Utility The SEER-HD Database Set-Up Utility provides options to perform one or more of the following tasks: 1. Create or upgrade an instance of SEER-HD Database. (SQL Server or SQL Express must be installed prior to creating a database.) 2. Configure an ODBC data source, on the local machine (i.e., the machine where the utility is run), corresponding to the newly created or upgraded SEER-HD database. 3. Set the default SEER-HD database, on the local machine (i.e., the machine where the utility is run), to the newly created or upgraded SEER-HD database. - 26 -

1. Create New Database If you do not have SQL Server or SQL Express installed locally or available on a network, you will be unable to create a database. Make sure that you have the required administrative privileges to create a database. The installer warns you that you need these before your proceed. Setup Folder The installer requires you to create a folder in which setup scripts and SQL Server log files will be placed (in case there is any problem with your installation). The default directory is <Program Files>\SEER\SEER- RDB. (The SEER-RDB folder is a holdover from when SEER-HD was named SEER-RDB.) There is normally no reason to change this, but you may. - 27 -

The installer creates a specific subdirectory for each new or upgrade version of the database. This subdirectory contains two further subdirectories, DBsetup for the database creation scripts and Outputs for the log files. The database setup log is the file DbSetupLog.txt in the Outputs subdirectory of the RDB versioned directory. The SQL Server database files themselves are installed in the Data subfolder of your Microsoft SQL Server Program s Server directory for SEER-HD, wherever that is defined. - 28 -

Create Database Dialog Sequence Choose DBMS Server Dialog The Choose DBMS Server dialog asks you to log on to the Server where you intend to create the SEER- HD database. SQL Server Instance Name: The drop-down box lists all servers available to the user on the NETWORK. (local) SQL Server instances, however, are not represented with complete names. For a local server instance, you must complete the Instance name yourself. For example, if you installed the SQL Express as SQLEXPRESS (the default local server name), you need to complete the (local) selection by adding the instance name with a backward slash before it: - 29 -

SQLDEV1 (local)\sqlexpress (network server name) (completed local server name) Log On: SEER applications do not currently support SEER-HD database access via SQL Server user and password authentication. While you may create a database using SQL Server authentication, you must create a Data Source Name (DSN) later using Windows authentication. Administrators should see "Network and Database Server Access" below for instructions on setting Windows user access on SQL Server or SQL Express databases. Connect with Windows authentication using the network login ID Your SQL Server administrator must have granted login privileges for your Windows login ID to access the SQL Server. If you have and older SEER-RDB already installed a local instance of MSDE, you should automatically have Windows Authentication access to the SQL Server instance if you log on to your computer with administrator privileges. SQL Server and SQL Express require that you add Windows users from within the SQL Management console. If you select this option, the SQL Server Login ID and Password text boxes will be grayed out. Connect with SQL Server authentication using a login ID and password If you have SQL Server authentication access to SQL Server or SQL Express, you may enter your SQL Server user ID and password. However, it is recommended that you use Windows authentication. If you continue on to create a DSN using SQL Server authentication, the DSN will not work with your SEER-HD applications, and will have to be reconfigured. DSNs currently require Windows authentication. Choose Database Name Dialog Enter the name of the SEER-HD database you wish to create. The default name is SEER-HD, but you may change it -- for example, to SEER-HD2, if you are creating a second SEER-HD database when one already exists. - 30 -

Database Name: Enter the name of the database you wish to create. Create ODBC Data Source for Database Dialog The Create ODBC Data Source dialog allows you to create a DSN for the SEER-HD database that you are creating. Creating a data source is optional, depending on whether the Create ODBC data source for database checkbox is checked or unchecked. If you have created the database using Windows authentication, you can continue on to create a SEER-HD DSN. If you have created a database using SQL Server authentication, you should uncheck the Create ODBC data source for database checkbox, continue on, and rerun the installer again to create a Windows authentication DSN using the Set Default DSN setup type. - 31 -

Create ODBC data source for database The Create ODBC data source for database checkbox is checked by default so that a DSN is created. If you uncheck the Create ODBC data source for database checkbox, NO data source will be created. You will have created a database that is not yet accessible to any SEER program. If you choose NOT to create a DSN, you can: 1. Rerun the installer and create a DSN later using the installer s Set Default DSN setup type option. 2. a. Created a DSN for the database manually using your computer s ODBC Administrator application. b. Select the DSN from within one of their SEER applications to make it the default SEER-HD database. Data Source Name (DSN) Enter the name of the DSN as you wish it to appear in the ODBC Administrator System DSNs dialog. If the DSN name you select already exists, the installer will ask you whether you want to replace it. Data Source Description Optional description of the DSN, normally to indicate its use. Some Notes on DSNs: If you create a new DSN name, you should proceed to setup type 3, Set Default SEER Historical Database, since the new DSN is NOT automatically registered as the default SEER- HD DSN/database. If you do not complete setup type 3, users will have to select the DSN from within their SEER program. If you replace your existing active SEER-HD DSN, it will now point to your new database. Because the active DSN is already recorded in the SEER-RDB DSN key, you do not have to complete step 3, Set Default SEER Historical Database. 2. Upgrade Existing Database Required Administrative Privileges The same administrative privileges are required for upgrading an SQL Server SEER-HD database as are required for creating a new one. Upgrade Database Dialog Sequence The database upgrade installer sequence for upgrading SQL Server databases is essentially the same as for creating them, except that the dialogs expect you to select an EXISTING SEER-HD database. See Create Database Dialog Sequence above. - 32 -

1. Choose DBMS Server 2. Choose Database Name 3. Create ODBC Data Source for Database Upgrade checks the version of the existing database against the version that is contained in the installer; it will run upgrade scripts only if the installer version is newer than the installed database. 3. Set Default SEER-HD Database The Set Default SEER Historical Database setup type allows you to switch SEER-HD DSNs without creating a database. The DSN name that you choose in this sequence becomes the ACTIVE default SEER- HD DSN that will be used by SEER programs. The setup utility must be run on the Local machine whose SEER-HD DSN registry value you wish to configure. This includes setting DSNs for remote databases. For a shared network database, the default SEER-HD database must be set individually on each user s local machine. Note that this setup type also allows you to set a SEER-HD Microsoft Access DSN so that you don t have to engage the Microsoft Access SEER-HD installer. If you have a Microsoft Access SEER-HD database installed, you may select it rather than an SQL Server SEER-HD. SQL Server DSN Creating an SQL Server default DSN involves the same sequence of dialogs as creating a new DSN, except that you are not given the option of NOT creating a DSN. See Create Database Dialog Sequence above. 1. Choose DBMS Server (use Trusted Windows Authentication) 2. Choose Database Name 3. Create ODBC Data Source for Database - 33 -

Remember that current versions of SEER-HD applications are unable to use DSNs with SQL Server Authentication. DSN authentication must be set to Windows Authentication ( Trusted ). If you select a DSN name that already exists, you will be asked whether you wish to replace it. Microsoft Access DSN To create a Microsoft Access SEER-HD DSN, you have to locate the SEER-HD Microsoft Access database file. Create DSN Creating a DSN for Microsoft Access SEER-HD is a one-step process, since the database does not have a DBMS Server or a Database Name (the MS Access file is the database name). Check DSNs The Check DSNs button is for checking the names of your SEER-HD database(s). You can also rename an old database if you want to use its name for the existing DSN that you created. Or you can delete and recreate DSNs. If you select a DSN name that already exists, you will be asked whether you wish to replace it. - 34 -

Configuring ODBC Data Sources Manually Using the Specify Repository menu option, advanced users can also select or configure SEER-HD data sources from within SEER programs that support SEER-HD databases. All that is required to create DSNs is that SEER-HD databases already exist. The following example demonstrates how to configure an SQL Server SEER-HD data source from within SEER-Compare. Similar configuration dialogs can be found in SEER for Software Microsoft Project Integration and other SEER-HD-enabled SEER applications. The Specify Repository option is under the Options menu. Selecting Specify Repository will raise the Specify Repository dialog, which tells you the DSN name of the currently active SEER-HD database. The Specify button raises the ODBC Manager application for selecting or creating new data source names. All SEER-HD database DSNs should be created under the Machine Data Source tab, which lists both System and User DSNs. - 35 -

If you press the New button, you will launch the ODBC manager, which enables you to create a new SEER-HD DSN from scratch. See Creating an SQL Server SEER-HD DSN with the ODBC Manager below for the steps for creating an SQL Server DSN from scratch. If you select a DSN and press OK, your SEER program will attempt to validate and set it as the default DSN. Microsoft Access Validation Microsoft Access SEER-HD databases raise the following login dialog. However, current versions of SEER- HD-enabled SEER applications do not support password protection on MS Access SEER-HD databases. Click OK without entering a Login name or Password. If database validation does not work, but you know that the database is SEER-HD, the database may be password protected and you will need to remove the protection. SQL Server Validation SQL Server SEER-HD databases raise the following login dialog. - 36 -

SEER-HD SQL Server databases in current versions of SEER applications work only with Trusted Windows authentication ( Trusted Connection ). Hence you should test the SQL Server DSN with Use Trusted Connection checked. NOTE: If the Use Trusted Connection checkbox is not checked when the login dialog appears, you should use the ODBC manager to try to change the DSN to Windows trusted authentication, then reengage Specify Repository to connect to the DSN. If you get the following connection error, you may have one of the following problems: 1. Your database is configured to work only with SQL Server authentication; the database and DSN have not been configured to work with Windows ( trusted ) authentication. 2. Your database is configured to work with Windows authentication, but not for the particular Windows logon profile that you are using. Each separate user needs to be configured as a database user within SQL server. See Access Control below. Creating an SQL Server SEER-HD DSN with the ODBC Manager Whether you invoke the ODBC Manager from within a SEER program or independently, the steps for creating a SEER-HD DSN are the same, although the ODBC Manager interface may look slightly different, depending on the version of it that you or the SEER program are using. DSN dialog sequence Create a System SQL Server data source The SEER-HD DSNs should be System data sources. User data source are available only to the user who created them and you would need to create a User data source for EACH user accessing the SEER-HD database. System DSNs are automatically accessible to all users. - 37 -

Select the SQL Server ODBC driver The SQL Server driver is necessary for configuring the SEER-HD DSN and communicating with the SEER- HD database. Driver Selection Results - 38 -

Enter a Data Source Name and select the Database Server Name: The name of the DSN that you wish to create. This is the name that will appear in the ODBC Manager s System DSN or Machine Data Source tab. Description: Optional. Some description that identifies the purpose of the database. Normally SEER Historical Database. Server: The SQL Server on which the database is located. Authentication Mode You must connect to the SQL Server before you are able to select the particular database to which you wish to connect. Windows Authentication: Uses your Windows network login ID (how you log on to your computer). SQL Server Authentication: Uses a login ID and password that have been configured in SQL Server. - 39 -

NOTE: Current versions of SEER-HD enabled applications are unable to use SQL Server Authenticated DSNs. You should always set Windows Authentication. Select the Database Once you have logged onto the particular SQL Server where the database is located, you need to select the database in the Change the default database to: option. Leave Use ANSI quoted identifiers and Use ANSI nulls, padding and warnings checked. The SEER-HD database is ANSI-compliant. Further Options The following dialog contains further options. Galorath-distributed databases are English language. You should pretty much leave other settings as is also (see dialog). If you choose to turn on ODBC logging, you will slow down the time that your SEER programs require in order to run the SEER-HD database. However, logging is useful if you ever encounter any errors in SEER-HD database retrieval; you can set it later if you run into any problems. - 40 -

Validate Database The final ODBC dialog is for testing the database to determine whether or not the DSN connection will work. Press the Test Data Source... button to finish creating the SQL Server SEER-HD data source connection. Results - 41 -

Access Control Access control for a SEER-HD SQL Server database, like most other database, is managed through a combination of access controls on the network, on the database server machine, on the DBMS, and on the SEER-HD database. Network and Database Server Access Access controls on the network and on the database server machine are beyond the scope of this document, and they are the responsibility of the user s IT organization. DBMS Access SQL Server and SQL Server Express SQL Server and SQL Express support two authentication modes for access to the DBMS: Windows network authentication and SQL Server authentication. Current SEER programs support only Windows authentication for accessing SEER-HD databases on SQL Server. This section describes how to grant a Windows user access to an SQL Server or SQL Express instance. For related information on the configuration of ODBC data sources, see the section Creating an SQL Server SEER-HD DSN with the ODBC Manager. Using Windows Network Authentication To use Windows network authentication to access a SEER-HD database on SQL Server or SQL Express no SQL Server logins need to be created. However, each user s Windows network login needs to be added, as a Windows User, to the target SQL Server or SQL Express. For details, refer to the Microsoft SQL Server 2000 or 2005 documentation. The following example demonstrates how to grant a user s Windows network login access to an SQL Server or SQL Express instance, using the SQL Server Enterprise Manager. Under the Server name, select Logins beneath the Security section: - 42 -

Add the Domain and User, select Windows Authentication, and grant access: SQL Server Authentication SEER-HD applications do not currently support SQL Server authentication. Mixed-Mode Authentication You may set both Windows authentication and SQL authentication for your users, but SEER-HD applications will use only the Windows authenticated login. For details on setting SQL Server authentication, refer to Microsoft SQL Server 2000 or 2005 documentation. - 43 -

Database Access SQL Server and SQL Sever Express For each Windows user who needs to access a SEER-HD database on SQL Server or SQL Express a Windows authentication database user must be created on that database. In addition, each user s user name needs to be associated with (i.e., given access from) the user s login to the SQL Server or SQL Express instance, with the minor variations described below. For details, refer to the Microsoft SQL Server 2000 or 2005 documentation. Using Windows Network Authentication To use Windows network authentication, each user s database user name needs to be associated with that user s Windows network login, in the target SQL Server or SQL Express instance. The following example demonstrates how to create a database user on a SQL Server database, and associate it with a user s Windows network login, using the SQL Server Enterprise Manager. Select the SEER-HD database under the Server name and select Users under the database name: Enter a new Domain User and select the public role. - 44 -

SQL Server Authentication SEER applications do not currently support SQL Server SEER-HD database access via SQL Server authentication. Default SEER-HD Database Role When a new SEER-HD database is created from the SEER-HD SQL Server Database Set-Up Utility, a default database role for SEER-HD users -- named SeerRdbUser -- is created on the new database. The SeerRdbUser database role is granted all of the table access permissions required by SEER-HD applications. ( SeerRdbUser is a holdover from when SEER Historical Databases were called SEER-RDB SEER Repository Databases.) Assigning Users to Default Database Role The simplest way to insure that a SEER-HD user has all the table access permissions required by SEER-HD applications is to assign the SeerRdbUser database role to the database user created for that SEER-HD user. The following example demonstrates how to use the SQL Server Enterprise Manager to assign a database role to a database user, using the Database User Properties dialog. Note that the database role can also be assigned at the time the database user is created, from the same Database User Properties dialog. Select the database user that you created in the last step and right click to raise the context menu and select the Properties option: - 45 -

Check the SeerRdbUser database role to assign it to the database user: You can also assign a database user to a database role by selecting the Role (rather than the User), raising the right-click context menu, selecting Properties, and adding a User. Select Roles under the database, right click over the SeerRdbUser role to raise the context menu and select Properties: - 46 -

Use the Add button to add the User that you created in steps above: - 47 -

Granting Explicit Table Permissions to Users Alternatively, individual table permissions can be granted to the database user created for each SEER-HD user. To insure that a SEER-HD user has all the table access permissions required by SEER-HD applications, grant to each database user all of the permissions granted to the SeerRdbUser database role. - 48 -

Database Backups Regularly scheduled backups of SEER-HD databases containing critical data are strongly recommended. Database Transactions and Rollbacks SEER programs do not support database transactions and rollbacks of SEER-HD databases. Therefore, backups of SEER-HD databases, especially when they are being edited by SEER-HDA, are particularly important. Data Recovery General Data Corruption If a general data corruption occurs in a SEER-HD database, data should be recovered from the most current database backup. Incomplete Project Revision Data In the event data for a SEER-HD database is only partially saved, due to a network failure or other systemrelated failure, please contact technical support at Galorath Incorporated. Removing SQL Server Express Instances If you have created SQL Server Express instances of SEER-HD that you no longer want to support on the computer, you may remove them using the Add/Remove application feature of your computer s control menu. Each instance has its own server name in parentheses. Removing the instance of SQL Server Express also removes any databases that were installed on the Server. Hence you should physically backup any database files if you wish to preserve them. - 49 -