Microsoft SQL Server setup

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.

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.

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.

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 Next >.

In the Instance Configuration panel, select
Named instance: and type
PDXPERT, and make sure the
Instance ID: is also
PDXPERT.
Click Next >.

In the Server Configuration panel,
assign the SQL Server Database
Engine's Account Name as
NT AUTHORITY\SYSTEM.

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
Add Current User button.

Add the SYSTEM as a SQL Server administrator:

Click the Add... button.

In the Select Users or Groups
window, enter SYSTEM into the
textbox, and click the OK button.

Click Next >.

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 the Windows Control Panel >
Administrative Tools >
Services, select the
PDXpert Server. Right-click and select
the Properties command. Select the
Log On tab, then select
This account: and enter the assigned Windows
administrator account (e.g., PDXSQL) and
password.
After clicking the OK 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.

Notes

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.