PDXpert PLM Software Installation Guide

Advanced install: Microsoft SQL Server

The PDXpert Server installer automatically downloads and installs SQL Server Express Edition ("SSEE"), the PDXpert Application Server service and the user interface console. If you're using the PDXpert installer's default SSEE, then you can skip this section and proceed to Advanced install: PDXpert application server. The SSEE installation will not conflict with any existing SQL Server instances on the same machine.

If you choose to install your own SQL Server database server instance, you must separately obtain and install your SQL Server version before installing the PDXpert Application Server. You should be familiar with the procedures for a custom installation.

If you intend to use...	Then you will...
The default SQL Server Express Edition	Skip this topic. Go to Advanced install: PDXpert application server
A 32-bit version of Windows	Install a 32-bit version of SQL Server
A 64-bit version of Windows	Install a 64-bit version of SQL Server

Do not use SQL Server's default installation settings. PDXpert requires a custom SQL Server configuration that can be configured only during install. A default installation doesn't support changes to the required settings, and you will have to uninstall, and then reinstall, SQL Server.

Do not install SQL Server on a compressed, network-mapped, or external (e.g., USB) volume.

Do not install another application's database into the PDXPERT instance.

Notes for installing all versions of SQL Server

• The SQL Server database instance must be installed on the same computer that you'll use for the PDXpert Application Server
• The SQL Server database instance must be named PDXPERT
• The SQL Server database instance must use the local System account (NT AUTHORITY\System) with SQL Server authentication and Windows authentication (also called Mixed Mode)
• The SQL Server database instance must have its TCP/IP protocol enabled

Additional notes for SQL Server 2008 R2 Express

• Do not use the Microsoft Web Platform Installer (www.microsoft.com/express/sql/download/) to install the SQL Server Express database engine. It does not allow any custom settings.

• Windows Installer 4.5 is a prerequisite for SQL Server 2008. This may require a separate download for your operating system before running the SQL Server 2008 installer.

• The prerequisites for SQL Server 2008 R2 go beyond those for SQL 2005. Before installing SQL Server 2008 for use with PDXpert, read "Hardware and Software Requirements for Installing SQL Server 2008" at http://technet.microsoft.com/en-us/library/ms143506.aspx

• If installing SQL Server 2008 R2 Express, you will need to customize the installation. For selecting the proper installer, go to Installing SQL Server 2008 R2 Express: http://blogs.msdn.com/b/petersad/archive/2010/04/26/installing-sql-server-2008-r2-express.aspx

  Select the correct version of "Microsoft® SQL Server® 2008 R2 Express" based on your Windows edition: X86 (32-bit), X64 (64-bit).

SQL Server 2008 R2 Express installation example

We installed Express editions of SQL Server 2008 R2 on a new, fully updated ("clean") Windows operating system. Since Microsoft can change SQL Server and operating system configurations at any time, and your computer may have existing application, database, anti-virus, firewall and other software, consider the following as a guide for those already familiar with SQL Server installation.

To install SQL Server 2008 R2 Express:

1. After the SQL Server Installation Center is displayed, click the "New SQL Server stand-alone installation..." option. After several panels, you'll be presented with the Feature Selection panel. Mark the Database Engine Services checkbox. PDXpert does not require any other optional features.

2. In the Instance Configuration panel, select Named instance: and type PDXPERT

3. In the Server Configuration panel, the Service "SQL Server Database Engine" should be assigned the Account Name as NT AUTHORITY\SYSTEM. If you're installing a PDXpert release 6.1 or earlier, then you must set the "SQL Server Browser" Startup Type to be Automatic.

4. In the Database Engine Configuration panel's Account Provisioning tab:

   • Select the Mixed Mode radio button, enter and confirm a strong password (this will be later overwritten, so it's not important what you use).
   • If there's no user account displayed, click the Add Current User button.

5. After the installation is complete, you can verify that the configuration settings are correct by opening the Summary.txt log file, typically located at C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log

   In particular, note

   • the INSTANCEID and INSTANCENAME are both PDXPERT
   • the SECURITYMODE is SQL
   • the SQLSVCACCOUNT is NT AUTHORITY\SYSTEM

   For PDXpert releases earlier than 6.2, the BROWSERSVCSTARTUPTYPE should be AUTOMATIC.

6. Close the SQL Server 2008 R2 Setup and SQL Server Installation Center windows.

7. The SQL Server 2008 R2 installation does not provide an option for enabling TCP/IP protocol. After you have completed the installation process, enable the TCP/IP protocol using the SQL Server Configuration Manager:

   1. From the Windows Start menu, choose All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager.

      If you don't see this menu option, you can open the Configuration Manager by right-clicking My Computer (XP) or Computer (Windows 7) in the Start menu and choosing Manage. In the Computer Management window, expand Services and Applications, expand SQL Server Configuration Manager.

   2. Expand SQL Server Network Configuration and then select Protocols for PDXPERT

   3. In the list of protocols displayed in the central panel, the TCP/IP protocol should be enabled. If you see that the TCP/IP protocol is disabled: click the TCP/IP protocol to select it, and then select Enable from the Action menu or context menu. The status column and icon for the protocol will change to show that the protocol is now enabled.

      .

   4. Close the SQL Server Configuration Manager window, and restart your computer to refresh the configuration.