Installation Guide

PDXpert PLM Software Installation Guide

Moving your PDXpert PLM database and file library

Introduction

You may want to move the PDXpert data to a new computer when you change the operating system or SQL Server edition (from, say, Express to Standard edition, or from SQL 2008 to SQL 2012), or convert from a single-user to multi-user system.

How PDXpert stores your data and files

Your new computer's SQL Server version must be equal to, or later than, the old system's SQL Server. For example, if the old server uses SQL Server 2008 R2, then the new server must have SQL Server 2008 R2 or SQL Server 2012: it cannot have SQL Server 2005 or SQL Server 2008. Before running the PDXpert installer on the new server computer, you may need to manually install the most current SQL Server release.

The PDXpert database stores information about documents, parts and change forms. The database also contains the collection members; administrator-defined operating rules; license and user account configuration; and system-managed "housekeeping" data.

Files that have been attached to these items are stored within a separate Library folder, with references to these files stored in the database. A library file is simply a copy of the original file, renamed to ensure uniqueness.

Other system data, such as the search index, is also stored outside the system database but this data is recreated on demand, and therefore will not be moved.

Determining your system's file library location and size

If you're moving a recently-created PDXpert system, and the Library folder therefore has few files, you can skip this section and jump to Moving a system with relatively small library.

The PDXpert Application Server console on your current server computer displays the location of your database and library. Open the PDXpert Application Server console and, on the Manage tab, note the location shown to the right of the Change Data Directory button. This is the current location of the Data folder.

PDXpert data folder location

To determine your system library folder's size, open your current server computer's Windows Explorer, and navigate to the Data folder. Within the Data folder is a \Library subfolder. Right-click on this \Library folder, select Properties from the context menu, and note the Size or Size on disk properties.

Data and Library folder location

Moving a system with a large library

When you have a large library (say, more than 1 GiB), then it may be faster and more reliable to move the PDXpert database and the library folder separately.

  1. Ensure that all users are logged out of their client workstations.

  2. On the old server computer, back up your database using the optional type Database without Library (*.bak). Note the name and location of the saved backup .bak file.

  3. On the new server computer, install your PDXpert Application Server software.

    Ensure that the new server's SQL Server version is compatible with your database from the previous server.

  4. Use Windows Explorer to copy the library files from the old server computer \Library folder (a) across the network directly to your new server computer \Library folder, or (b) to a backup disk or USB drive and then onto the new server computer. Each server computer's \Library folder will be located within the server data folder as described above.

    If you're also upgrading the PDXpert system, it's essential that you copy the library files before restoring the database backup file. The library files' hash values may need to be recalculated during the upgrade, which requires the physical files.

  5. Copy the backup .bak file from the old server computer onto a local drive on the new server.

    Do not attempt to restore the database across the network from a mapped drive. The restore operation will fail.

  6. Use the PDXpert Application Server console on the new server computer to restore the database.

You're now ready to validate the moved database and library.

Moving a system with relatively small library

This procedure describes how to move the PDXpert data when you have a small library (less than 1GB).

  1. Ensure that all users are logged out of their client workstations.

  2. On the old server computer, back up your database using the default type Database with Library (*.pdxz). Note the name and location of the saved backup .pdxz file.

  3. On the new server computer, install your PDXpert Application Server software.

    Ensure that the new server's SQL Server version is compatible with your database from the previous server.

  4. Copy the backup .pdxz file from the old server computer onto a local drive on the new server. Do not attempt to restore the database across the network from a mapped drive. The restore operation will fail.

  5. Use the PDXpert Application Server console on the new server computer to restore the database.

Validating your database & library upgrade

Use the following steps to confirm that your database and library file pointers have been successfully updated.

  1. Start the PDXpert client using an account with sufficient role permissions:

    • Enter account name, password, and new server computer's name or IP address, and

    • Click the OK button.

  2. Within the PDXpert client, search for a known part or document that has a file attachment. Open the item and confirm that the file attachment can be copied from PDXpert to your computer's Desktop. View the file to ensure the file appears as expected. You may want to test both recent and older items.

    A large database may require significant time before all items are searchable. You can monitor indexing progress within the PDXpert client: Tools | Index Status...

Uninstall your previous PDXpert Application Server

After the new system has been verified as working correctly, uninstall the PDXpert Application Server from the old server machine to ensure that no one mistakenly connects to the obsolete database.

If you wish, you can then install the PDXpert client to connect to the new server.

Post-installation

Ensure that you have a frequent and reliable automated backup process.

Some antivirus software can interfere with the PDXpert Application Server, and should be tested for problems while users perform normal database and library file tasks (especially during attaching large or compressed files). If in doubt, exclude the PDXpert data folder from antivirus scanning.

See Important post-installation considerations.