Moving your PDXpert PLM database and file library

Last update 2022-10-12

Introduction

You may want to move PDXpert data to a different computer when you change the operating system or SQL Server edition (from, say, Express to Standard edition, or from SQL 2014 to SQL 2019), or convert from a single-user to multi-user system, or copy production data into a test server.

In this topic, the source computer contains existing database and library files that are copied to the target computer. The target may be a new production server computer or an existing development, test or user training system.

Your target computer's SQL Server version must be equal to, or later than, the source system's SQL Server. For example, if the source server uses SQL Server 2019, then the target server must have SQL Server 2019 or later; it cannot have SQL Server 2014 or SQL Server 2016. Before running the PDXpert installer on the target server computer, you may need to manually install the compatible SQL Server release.

Similarly, the target server's PDXpert release must be the same as, or later than, the source system's PDXpert release.

Before beginning: Use the PDXpert client to check that the source system uses the most recent software license key. The PDXpert release installed on the target system must be compatible with the software license.

Do not use SQL Server commands to attach database MDF/LDF files copied from another PDXpert system; this can damage your data. To ensure client cache coherence, each database must have a unique database identifier ([PDXpertInfo].[DatabaseId]). The PDXpert Server assigns a new identifier when it the restores the database; the SQL Server ATTACH command does not.

How PDXpert stores your data, license key, and files§

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

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.

If your company has made changes to the source computer's PDXpert.Service.exe.config file, the settings may need to be copied into the target server computer's PDXpert.Service.exe.config file.

Determining your system's database & library location and size§

The PDXpert Application Server console on your source 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's size, open your source server computer's File Explorer, and navigate to the Data folder.

Windows normally hides the ProgramData folder. If the data directory is C:\ProgramData\PDXpert\Data then you may need to view hidden items in File Explorer.

Within the Data folder are several subfolders. We need to move only these two:

  • Note the size of the files contained in the \Database subfolder.

  • Check the values of the files contained in the \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 "small" system§

This procedure describes how to move your PDXpert data when you have a combined database and library of less than 2GB.

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

  2. Check that the email queue is empty. If it is not empty, wait until it's empty, or click the Delete all button. This prevents any unexpected emails to be sent when the database is restored to the new server.

  3. On the source 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.

    If the backup dialog doesn't let you save the backup as a PDXZ file, but only as a BAK file, then follow the instructions for moving a large system in the next section.

  4. On the target server computer, install your PDXpert Application Server software. Use the default install procedure or the advanced install procedure.

    The target server's SQL Server version must be compatible with your database from the source server.

    The target server's PDXpert release must be the same as, or later than, the source server.

  5. Copy the backup .pdxz file from the source server computer onto a local drive on the target server. Do not restore the database from a mapped network drive. The restore operation may fail.

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

  7. After installation, review the PDXpert Application Server post-installation checklist.

    To send workflow and task notifications, your SMTP server must accept emails from the new server machine. For configuration information, see the Setting up the email account help topic.

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

Moving a "large" system§

When you have a large database and/or library (more than about 2 GiB), then you'll move the PDXpert database and the library folder separately.

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

  2. Check that the email queue is empty. If it is not empty, wait until it's empty, or click the Delete all button. This prevents any unexpected emails to be sent when the database is restored to the new server.

  3. On the source 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.

  4. On the target server computer, install your PDXpert Application Server software. Use the default install procedure or the advanced install procedure.

    The target server's SQL Server version must be compatible with your database from the source server.

    The target server's PDXpert release must be the same as, or later than, the source server.

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

    Copy the library files before restoring the database backup file. The library files' hash values may need to be recalculated, which requires the physical files.

  6. Copy the backup .bak file from the source server computer onto a local drive on the target server.

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

  7. Use the PDXpert Application Server console on the target server computer to restore the database.

    Do not use SQL Server Management Studio or SQL Server commands to restore the database. The PDXpert Server must assign a new identifier when it the restores the database.

  8. After installation, review the PDXpert Application Server post-installation checklist.

    To send workflow and task notifications, your SMTP server must accept emails from the new server machine. For configuration information, see the Setting up the email account help topic.

Validating your moved database & library§

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

If your company has made changes to the source computer's PDXpert.Service.exe.config file, review these to decide if any settings should be copied into the target server computer's PDXpert.Service.exe.config file. The settings may need to be adjusted for the new environment. See the PDXpert service configuration settings topic.

The software license key and user log-in accounts are stored in the database, and moved to the new server when the database is copied.

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

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

    • Open the Options, and mark the Reset my account settings option.

      The user must always mark Reset my account settings option when moving between the source and target servers. Or, the database unique identifier must be changed using a SQL query. See the following section Converting the source system to a test server.

    • Click the OK button.

  2. If you're prompted for a license file, import the current license key file.

  3. If you've moved a large system, open the Index Status window: Tools ➔ Index Status... command. Click the Re-index button. A large database may require significant time before all items are searchable.

    If you've moved a small system, re-indexing automatically begins after the database is restored. You can check the indexing progress using the Index Status window.

  4. Use the Item Explorer to search for a known part or document that has a file attachment; or, select a similar item from the Recent list. 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.

  5. Check that email notices are received as expected.

Converting the source system to a test server§

After the new system has been verified, the source system can be uninstalled (see the next section).

However, if you want to use the source for report development, import testing, upgrade verification, user training, or other purpose, see Managing a PDXpert test server.

A test system's database must be adjusted before it can be used alongside the production system. The production database can be damaged if you don't correctly configure the test system.

Uninstalling the source server§

After the target system has been verified as working correctly, uninstall the PDXpert Application Server from the source server machine. This ensures that

  • no one mistakenly connects to the obsolete database, and
  • all system components remain compatible — the target server can update a PDXpert client, but it cannot update another server.

If you wish, you can then install other PDXpert clients to connect to the target server.

On each client log-in window, remember to use the target server's name.