PDXpert PLM Software
Microsoft SQL Server setup
Last update 2017-08-23
The PDXpert System Setup installer automatically downloads and installs SQL Server, the PDXpert Application Server and a PDXpert client application. For example, PDXpert 10.0 (and later) installs SQL Server Express LocalDB. This is a secure, low-profile, minimal footprint version of SQL Server. It's intended to support workgroups of up to about 10 users. The installation is fast, and won't affect other database applications.
If you choose to install your own SQL Server database server instance, then install it before1 installing the PDXpert Application Server.
|If you want...||And your operating system is...||Then you will...|
|The default SQL Server Express or LocalDB2||Any compatible version of Windows or Windows Server||Skip this topic. Go to Custom installation: PDXpert application server|
|SQL Server Workgroup, Standard or Enterprise Edition||A 32-bit version of Windows or Windows Server||Install the 32-bit version of the desired SQL Server edition|
|SQL Server Workgroup, Standard or Enterprise Edition||A 64-bit version of Windows or Windows Server||Install the 64-bit version of the desired SQL Server edition (unless you have an existing 32-bit version installed)|
Notes for installing SQL Server Express or higher
Do not use SQL Server's default installation settings. PDXpert requires SQL Server settings that can be configured only during a custom 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 read-only, compressed, network-mapped, or external (e.g., USB) volume. Do not install SQL Server on a Domain Controller.
The PDXpert Application Server asserts full control over its instance. The instance may be restarted after an upgrade. Consider creating a separate instance to isolate PDXpert activities from other database applications.
Do not create new objects (e.g., views) within the PDXpertDB database, since unrecognized objects may interfere with proper operation or be deleted during upgrade.
After all tasks are finished, check for SQL Server updates from Microsoft's website.
This topic decribes how to install SQL Server Express or a higher version. Install SQL Server LocalDB using the standard settings.
- This page summarizes the most important SQL Server installation instructions. Complete information is available on the Microsoft web site.
- Before installing SQL Server for use with PDXpert, read Microsoft's Hardware and Software Requirements for Installing SQL Server. Note that Windows Installer creates temporary files on the system (typically C:) drive. Before you install or upgrade SQL Server, verify that you have enough disk space on the system drive for these files. Even if you install to a non-system drive, SQL Server requires space on the system drive.
- Windows Installer 4.5 is a prerequisite for recent SQL Server versions. This may require a separate download for your operating system before running the SQL Server installer.
- 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 use the local System account (NT AUTHORITY\SYSTEM) with SQL Server authentication and Windows authentication (also called Mixed Mode). If your SQL Server administration policies do not allow the use of the Local System account, then you must follow the alternative procedure (below).
- For PDXpert releases 9.3 and earlier, the SQL Server database instance must be named PDXPERT and have its TCP/IP protocol enabled.
Installing on computers that already have SQL Server Express or higher
You can install a new SQL Server instance on a computer that already has SQL Server installed.
Different SQL versions (say, SQL Server 2008 R2, 2012 SP3 and 2016) and different SQL editions (for example, SQL Server Express and SQL Server Enterprise) will work on the same machine.
There is one exception: If you have a 64-bit version of Windows with 32-bit SQL Server already installed, do not use the PDXpert system installer to install SQL Server. Manually install a new instance of 32-bit SQL Server using the configuration values — local system account, mixed mode authentication, etc. — described on this page. The PDXpert System installer relies on Windows' 32b/64b configuration to determine which SQL Server Express to download from Microsoft, and we've seen that 32b and 64b SQL Server instances don't work well together.
If possible, install the new SQL Server instance using the same Windows administrator account that was used to install the existing SQL Server instance.
If you're accessing PDXpert database views in the SQL Server PDXPERT instance, and another SQL Server instance exists on the server, then enable the SQL Server browser service. Otherwise, PDXpert doesn't require the SQL browser.
SQL Server installation example
SQL Server Express download
Download the desired SQL Server Express option.
- 2014 SP2: https://www.microsoft.com/en-us/download/details.aspx?id=53167
- 2016 SP1: https://go.microsoft.com/fwlink/?LinkID=799012
Express installers for 64b and 32b Windows (English language) are named:
- 64-bit Windows: SQLEXPR_x64_ENU.exe
- 32-bit Windows: SQLEXPR_x86_ENU.exe
- SQL Server 2016 can only be installed on 64-bit Windows: SQLServer2016-SSEI-Expr.exe
Installation procedure using the local System account
In this example for 64-bit Windows, SQL Server 2016 Express edition is installed on a new, fully updated Windows Server 2016 operating system.
After starting the SQL Server installer, select the Custom option and click the button. (This panel isn't displayed when installing SQL Server 2014 or earlier.)
After the SQL Server Installation Center is displayed, click the New SQL Server stand-alone installation… option. This opens a separate SQL Server Setup wizard.
After several panels, you'll arrive at the Feature Selection panel. Mark the Database Engine Services checkbox. PDXpert does not require any other optional features or directory settings. Click .
In the Instance Configuration panel, select Named instance: and type PDXPERT, and make sure the Instance ID: is also PDXPERT. Click .
In the Server Configuration panel, assign the SQL Server services:
- Agent (if displayed): Account Name as NT AUTHORITY\SYSTEM with the startup type as Automatic.
- Database Engine: Account Name as NT AUTHORITY\SYSTEM with the startup type as Automatic.
- Browser: Account Name as installer's default value, and the startup type as Automatic.
If your system doesn't offer the NT AUTHORITY\SYSTEM account, add a new Windows administrator account.
In the Database Engine Configuration panel's Account Provisioning tab:
- Select the Mixed Mode radio button, then enter and confirm a strong password, like 1qwe!ASD The PDXpert Server will overwrite this later, so you don't need to keep a record of it.
- If there's no user account displayed, click the button.
- Add the SYSTEM as a SQL Server administrator:
In the Select Users or Groups window, enter SYSTEM into the textbox, and click the OK button.
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\version\Setup Bootstrap\Log (for SQL Server 2016, version is 130; for 2014 is 120; and for 2012 is 110).
In particular, note
- the INSTANCENAME is PDXPERT
- the SECURITYMODE is SQL
- the SQLSVCACCOUNT is NT AUTHORITY\SYSTEM
Close the SQL Server 201… Setup and SQL Server Installation Center windows.
Installation procedure using an assigned Windows administrator account
Modify the SQL Server installation procedure (above) if your SQL Server administration policies don't allow applications to use the Local System account:
Create a new Windows user account (for example, PDXpertAdmin) and assign a password. Change the account type to Administrator.
Install SQL Server as above. During installation:
In the Server Configuration panel, assign the SQL Server Database Engine's Account Name as the Windows administrator (e.g., PDXpertAdmin) with the assigned password.
In the Database Engine Configuration panel's Account Provisioning or Server Configuration tab, click the button, then enter the Windows administrator account (e.g., PDXpertAdmin).
After SQL Server has been installed, install PDXpertSystemSetup.exe using the db=0 command line option.
In the Windows Control Panel > Administrative Tools > Services, select the PDXpert Server. Right-click and select the command. Select the Log On tab, then select This account: and enter the assigned Windows administrator account (e.g., PDXpertAdmin) and its password. After clicking the button, restart the PDXpert Server service (if prompted, accept restarting the PDXpert Filter Service).
Open the PDXpert Server window.
- On the Manage tab, note the data directory (typically similar to C:\ProgramData\PDXpert\Data\). Ensure that the Windows account has full read/modify/delete permissions for the PDXpert data directory and its subfolders.
- Select the installed SQL Server.
Firewall and TCP/IP for external communications
For releases prior to PDXpert 8.0, and for any system that shares data with other applications via user-defined views, your server's firewall for SQL Server must be open and SQL Server's TCP/IP protocol enabled.
To enable the TCP/IP protocol using the SQL Server Configuration Manager:
From the Windows Start menu, choose All Programs, point to Microsoft SQL Server 201…, point to Configuration Tools, and then click SQL Server Configuration Manager.
In the Sql Server Configuration Management window, expand the SQL Server Network Configuration node, and then select Protocols for PDXPERT.
In the list of protocols displayed in the main panel, the TCP/IP protocol must 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.
Close the Sql Server Configuration Manager window. Reboot your computer — or restart the SQL Server (PDXPERT) service — to refresh the configuration.
The PDXpert 10.0 (and later) system setup offers a command-line option that allows the SQL Server instance to be selected after the PDXpert application server is installed.
PDXpert system releases install different SQL Server Express versions:
PDXpert 10.3 (and later) installs Express 2014 LocalDB.
PDXpert 10.0 through 10.2 installs Express 2012 LocalDB.
PDXpert 8.0 through 9.3 installs Express 2008 R2.
PDXpert prior to 8.0 installs Express 2005.
Install Guide Contents
- 001. Installation overview
- 002. Preparing the server computer
- 003. Standard PDXpert System setup
- 004. Standard PDXpert PLM client setup
- 005. Installing LocalDB for PDXpert client ODBC
- 006. Custom installation: SQL Server
- 007. Custom installation: PDXpert server
- 008. Custom installation: Private cloud
- 009. Custom installation: Group Policy
- 010. Upgrading the PDXpert Application Server
- 011. Upgrading the PDXpert PLM client
- 012. PDXpert server post-install checklist
- 013. Moving PDXpert server database and files
- 014. PDXpert Application Server diagnostics
- 015. PDXpert PLM client diagnostics
- 016. Microsoft SQL Server diagnostics
- 017. Microsoft SQL Server log files
- 018. Connecting SQL Server Management Studio
- 019. Upgrading SQL Server
- Installing and upgrading older PDXpert releases
- 023. Service configuration settings
- 024. Application folders and files
- 025. System architectural diagram
Release notes (change history)
- PDXpert 8.0 release notes
- PDXpert 8.1 release notes
- PDXpert 9.0 release notes
- PDXpert 9.1 release notes
- PDXpert 9.2 release notes
- PDXpert 9.3 release notes
- PDXpert 10.0 release notes
- PDXpert 10.1 release notes
- PDXpert 10.2 release notes
- PDXpert 10.3 release notes
- PDXpert 11.0 release notes
- PDXpert 11.1 release notes
- PDXpert 11.2 release notes
- PDXpert 12.0 release notes
- PDXpert 12.1 release notes