Setup for Optimized Performance SOLIDWORKS® PDM - SolidPractices

Best Practice Information

Domain and Role/Product

<a class="s6m-tag-link sm-link" data-predicate="ds6w:what" data-tag-value="SOLIDWORKS PDM" data-type="internal" contenteditable="false">SOLIDWORKS PDM</a> <a class="s6m-tag-link sm-link" data-predicate="ds6w:what" data-tag-value="Performance" data-type="internal" contenteditable="false">Performance</a> <a class="s6m-tag-link sm-link" data-predicate="ds6w:what" data-tag-value="ds6wclassifier:what_BELCHAR__#ct#_Data Management & PDM" data-type="internal" contenteditable="false">Data Management & PDM</a> 

What's Covered? - Jump to each section using the Contents List in the top right!

  • Data cards
  • Search & favourites
  • Categories
  • Workflows
  • Users & groups
  • Notifications
  • Replication
  • Cold storage
  • Archive data storage
  • SQL performance tuning
  • Installation and upgrades
  • Server & workstations upgrades
  • File version upgrades

 

Revision History

Rev #DateDescription
1.0Dec 2021Document created.
1.1June 2025Document update for SOLIDWORKS PDM 2025
 2.0Nov 2026Document formatted for 3DSwym
Note

All SolidPractices are written as guidelines. It is a strong recommendation to use these documents only after properly evaluating your requirements. The distribution of this document is limited to Dassault Systèmes SolidWorks employees, VARs, and customers that are on active subscriptions. You may not post this document on blogs or any internal or external forums without prior written authorization from Dassault Systèmes SolidWorks Corporation.

This document was validated using SOLIDWORKS PDM 2025 sp0 and Microsoft SQL Server 2022. If you have questions or need assistance in understanding the content, please get in touch with your designated reseller.

<strong>Acknowledgments</strong>
This document was authored by MLC CAD Systems and reviewed by Dassault Systèmes SolidWorks.

 

Your Feedback Requested

We would like to hear your feedback and suggestions for new topics. After reviewing this document, please take a few minutes to fill out a brief <a href="https://www.surveymonkey.com/r/SolidPractices" rel="nofollow">survey</a>. Your feedback will help us create content that directly addresses your challenges.

Preface

SOLIDWORKS PDM helps customers manage and organize design data and project information. To maximize the potential of SOLIDWORKS PDM we have outlined potential optimizations in several functional areas along with some behind-the-scenes tips and tricks to boost the performance of the whole system.

Because your valuable data is likely the backbone of production for your organization, we have also included a section that discusses backup automation. Included options for system restoration will quickly get you back on track again, should disaster strike.

The guide is a great place to begin for a small team just getting started with SOLIDWORKS PDM, and for the large multi-regional organization with several years’ experience. As your team grows, you will want to leverage further performance optimization techniques.

Your Value-Added Reseller (VAR) can be a great resource and likely has encountered many of the challenges you are running into. Their knowledge and understanding of the techniques found here can help elevate the performance of your design team, so please reach out to them to discuss challenges as they arise.

Use this document in combination with the instructions you find in the SOLIDWORKS PDM “Installation Guide”, “Administration Guide” and “Replication Guide” as well as other SolidPractices and Knowledge Base (KB) articles.

In the default SOLIDWORKS PDM installation, a PDF version of these guides is available in the following location:

C:\\Program Files\\SOLIDWORKS Corp\\SOLIDWORKS PDM\\Lang\\[Language]

Throughout the document, you will find references to the SolidPractices, which may be accessed from the link below or by searching for their Solution ID in the Knowledge Base.

 

 

Data Cards

SOLIDWORKS PDM data cards are extremely useful in storing data with documents that enter the vault. This usefulness extends to all files stored in the vault, not just SOLIDWORKS files. This functionality is also extended to Folder, Template, and Items. To leverage the data that is input by users and through automation, Search cards are used.

When a user inputs data onto a data card for a file, upon check-in, then data is updated in the database and searching can be used to find the file based on the input data. The input data can also be populated into the file, using SOLIDWORKS PDM variable attributes. Attribute mapping is covered extensively in the SOLIDWORKS PDM Administration Guide, found under Help > Administration Guide in the SOLIDWORKS PDM Administration tool.

One of many ways to reduce errors and accelerate data input is to utilize other data cards that have already been filled out. The folder card is one such example.

  1. Leveraging the Folder Card for Speed & Error Reduction

Windows explorer does not have the ability to attribute a folder, but SOLIDWORKS PDM does. Data that is input on a Folder card is searchable inside of the vault. An added benefit of users' input on folders cards is the ability to leverage that data for automated insertion on any file that is placed in that folder. Even just a few fields can result in hours per year of cost savings.

Setting up your folder card is the first step in leveraging this method. Include all pertinent project and/or job information:

File data cards used to capture data on the insertion or initial save to the vault can leverage the folder card data eliminating the need for the user to re-enter existing data. Instead, the file data card can ‘pull’ the data across and populate these fields automatically. This is performed through the addition of a Folder Data Card Default Variable value, which is accessible from when selecting a variable on the File or Template Data Card:

When this method is used on a File or Template Data Card, the resulting value auto-inserted will be from the contextual folder where the user currently has open or where the file is being saved.

Deploy this method liberally and your users will thank you for saving them countless hours of data re-entry along with seeing a dramatic reduction in errors.

  1. Card Design Tips & Tricks

The data card editor was designed to facilitate the use of variable data controls. Many of these mimic the data controls you might find in .Net Studio, or similar. As we begin to work with these controls, it is best to determine the overall design layout and account for any frames and tab controls that will be used. Once that is determined, the base layout of the card can be determined.

If you are using the default Windows Explorer vault view horizontal layout, then you will want to flatten out your data cards horizontally for the greatest user benefit. The reason behind this is that users will typically desire the largest possible file list view. Having 4-5 rows, or less, of variable information is best to optimize the user experience. Additional columns can be added to widen out the data card and offer additional input fields.

This layout is specified as ‘At the Bottom’ (Horizontal) under Preview Placement:

Using Display > Preview Placement > To the Right (Vertical), a user can alter the placement of the SOLIDWORKS PDM interface in Windows Explorer. This does alter the need for variable placement to be in 1-2 columns of data where more vertical space can be utilized.

You will notice that with a horizontal data card, more columns of information are visible alongside the files, while with a vertical data card more files are visible. The consensus among your company’s users will need to be reached for the placement used, as the design of the data card cannot be switched by the user.

  1. Do I have too many variables?

The easiest way to determine if you have too many variables in place on your file data cards is to perform a spot inspection of the data in the vault. Looking through the data you may start to see a pattern emerge where certain variables will not contain any data. This could be caused by a conscious or unconscious choice on the part of the users. Further investigation will be required if this is the case.

Why does having too many variables matter? Each time a variable is placed on the file data card, the user is expected to populate that field with useful information, or the system should be auto-populating it either on entry to the vault or upon workflow transition. Extraneous data fields on the card consume time from the user and require additional computing resources on the SOLIDWORKS PDM server(s).

Most file data cards contain less than 20 variables, which is a very reasonable quantity. In one use case, the data card contained 20 variables on 30+ tabs which were controlled by a category variable to determine which tab was active for a particular part type. This sounds great and would have been functional for the user, except all of the common variables were also included on each of these tabs. Here is an example similar to what that looked like, but please don’t do this:

The complication with this method is that each variable is queried when a user selects the file, including the variables that are not visible to the user. That means that 20 * 30 = 600+ variables are being queried every time a user selects a file, and the resulting performance is less desirable. What would make sense in this example, is to break out Part Type specific information and offer just 1-5 variables per Part Type to the user. This would optimize the card bringing the variable query count down to (5 * 30) +15 = 165 variables.

  1. Divisional or Regional Data Cards

As in the last example, many times it is necessary to use a category or type to control the visibility of variables on a data card. This would mean that for each different location and/or language used, you would need a tab with the same variables as the others. This causes additional computational load on the SOLIDWORKS PDM Server and can be mitigated.

Depending on the need, you may be able to structure the vault in such a way that each division uses its own root folder for files used by that division. In this case, it would be best to pare down the data card to only include the language and data variables used by that division, then to save that division's specific data card to their division folder.

When a data card is saved to a sub-folder, all files contained in that folder and below will use the division-specific data card with a sub-set of the overall variables. This offers some major benefits to the users in that folder, by reducing the overall variable count and also by limiting the database queries required for the presentation of file data in the vault view.

 

Search & Favorites

SOLIDWORKS PDM offers great power and flexibility in search functionality with the opportunity to use multiple search criteria. This allows the user to drill down to exactly the subset of data they are looking for. In the previous chapter, we covered the importance of limiting the file card variables to those that are receiving data. This becomes vitally important for users seeking out that data through search. As the old adage goes, ‘Good data in, equals Good data out’.

A good opportunity for every vault is to take the finalized file data card(s) and turn them into search cards. One such example is to turn the CAD File card into a CAD Search card. The only additional variables needed for making this a fully functional CAD Search card are obtained from the Complete Search card that is available under:

C:\\Program Files\\SOLIDWORKS Corp\\SOLIDWORKS PDM\\Default Cards

The procedure to provide this familiar search card is to open the CAD File card from the PDM Administration tool under Cards > File Cards. Then you will want to save the card as a Search Card using the ‘Cards of Type’ and give it an appropriate name that the user will use to open the search, such as ‘CAD Search’:

Then we will open the complete search and copy/paste the following fields onto our new CAD Search card:

  • Search Folder Path
  • Display folders
  • Display files
  • Name
  • Include subfolders
  • Search in all versions

You will also want to remove the read-only option from all variables, so users can input search criteria into all the variables. When complete, your search card will be similar to:

Any options that users regularly need to set can be automated, saving them time when performing the search. One example is turning off the ‘Display Folders’ option. This is performed from Card > Default Values or using the ‘Default Values’ button in the Card Properties dialog. Select the option ‘Find Folders’ and set the Value to ‘0’ (zero). This will uncheck the option each time at the start of the CAD Search card.

The only thing that remains is to set permissions for the groups that may use this new CAD Search card and to mark the view and preferred column set that should be presented back to the user when data is returned from the search.

  1. Using Search Operators

An underutilized option available to SOLIDWORKS PDM Users is Search Operators. Depending on the desired results, AND, OR, and NOT operators can be used to refine results. Input search criteria for any search card, search tool, quick search, or Web2 search can leverage the operators shown in the table below.

The default method used by SOLIDWORKS PDM is a wildcard search. When a term is encapsulated within * (star) symbols it functions the same way as without any symbols. So searching for Valve is the same as using *Valve*.

OperatorDescriptionExamples
*Wildcard*Valve*
*Valve
Valve*
" "Explicit string"4 in Gate Valve"
=Exact Entry=Valve
SpaceAll terms requiredGate Valve
ANDString containing bothGate AND Valve
&String containing bothGate & Valve
OREither valueGate OR Valve
|Either valueGate | Valve
For variables of a numeric or date type, the valid operators are: 
<Less than<5
>Greater than>3
<=Less than or equal to<=4
>=Greater than or equal to>=4
!=Not equal to!=5
   

Alternatively, the Variables tab on the Complete Search card can be used to provide multi-operator/multi-variable capabilities, such as combining OR operations with other operators on different variables.

  1. Managing Shared Favorites*

Favorite searches are a great way to assist users in pulling up common searches like ‘Files checked out by ’ or ‘Files Pending Approval’. Both of these are very common searches that should be deployed in your vault, but the question remains as to how you edit or administrate the permissions for a well-used search. You may also want to remove a search that is no longer needed to clean up and streamline the interface for users.

Using the Search Tool, accessed from Tools > Search Cards or from the Open Search > Search Tool command:

From the favorites area, you can access the properties or delete a favorite. And in the properties dialog you can add/remove group level access to the favorite:

Ensuring that users have rights to necessary favorites will help them in using SOLIDWORKS PDM efficiently, while not having to remember the specific setting(s) for a common search.

More information related to searching in SOLIDWORKS PDM can be found here:

SolidPractices: Searching in SOLIDWORKS PDM [QA00000121991]

* Search favorites are only available with SOLIDWORKS PDM Professional. 

Categories

When a file is checked into the vault several actions occur, one of which is categorization. Proper use of Categories* will assist you in guiding files to the proper workflow, or in advanced use cases helping to make the proper choice of multiple transitions so that different actions can be taken for different categories of files.

Categories can be based on:

• Filepath - file extension and/or folder location

• Variable data

• Object type

• Revision.

  1. Leveraging Categorization

There are two basic philosophies used when dealing with Categories. The first is filtering with an allowance for a particular category. This is the preferred method as it is the easiest method to use.

The second method is a negation method where ‘!=’ is used for all categories except for the desired one. While this method can operate correctly, it requires many more conditions to be applied and validated.

It may also be possible to leverage a hybrid approach of both methods, which is generally unnecessary, and in most cases, simplifying down to the allowance method for only the categories needed overcomes any issues encountered.

In the example below the design specification states that all ECO documents go into the ECO Workflow. To accomplish this a combination of settings is utilized, the Category for all files in the ECO root level folder is included using the file path of ‘ECO\\%’. This Category is then used in the properties of the workflow for the argument, which routes all documents with the ECO Category to the ECO Workflow.

Depending on the needs of your vault design, you may have to limit the Category to include only certain file extensions. Using an OR statement to include all the desired file extensions will allow any of these to be categorized with the Category. Using a secondary line to limit the location of the files is also possible. Notice in the example below that the CAD File Category includes all SOLIDWORKS, dxf, igs, iges, dxf, stp, and step files that are placed in the root level Engineering folder. Since the folder line is not included in the OR statement, it is an AND condition statement.

The overall design of the entire vault is performed this same way for all workflow conditions to ensure consistency in the application of Categories, with only one exception. There needs to be one Category and one Workflow without any conditions. This Category and Workflow, typically ‘-‘ and ‘Non-Revision Managed’ respectively are the catchalls. If the file does not meet the conditions of the other defined Categories, then it will enter into the ‘-‘ Category, and then into the ‘Non-Revision Managed’ workflow.

* Categories are only available with SOLIDWORKS PDM Professional.

 

Workflows

SOLIDWORKS PDM can be configured to match your existing business processes without the need to modify the business process to match the tool. Serial and Parallel approvals are possible with variable and revision updates occurring automatically during the process.

Normal operation of SOLIDWORKS PDM Workflows is covered extensively in the SOLIDWORKS PDM Administration Guide. You will find the methods for adding states and transitions, including applying permissions to both.

An easy way to determine when a state is needed is to visualize the document traveling around the office and when the document stops for a signature, or an action is needed, then that is when you need a state. Transitions connect these action and decision points (states) to provide a means of updating variable data and performing automated tasks.

SOLIDWORKS PDM Workflows should not be used for recording individual steps taken while a document remains under a single user's purview. This would cause unnecessary state changes and be inefficient for the user(s).

  1. Dealing with Existing or Acquired Data

Occasionally PDM and CAD Administrators need to deal with acquired data that may not yet exist in the current vault. While generally, it is easiest if custom properties and revision sequences are aligned, this is not always the case. In the case of misalignment, decisions will need to be made to handle these discrepancies. Once a determination is made, the mapping of existing revision levels and variable values can be recorded in a ‘from/to’ list for implementation in SOLIDWORKS PDM.

Also, it will be necessary to evaluate the source of the data being imported. An excellent reference guide related to file references and remediation can be found here:

SolidPractices: Importing Files from Folders [QA00000124636]

Once the acquired data is brought into the vault, it functions like existing file vault data. Considerations need to be taken concerning the file vault revision and variable data. The file vault revision is not the same as the revision on the data card but can be. SOLIDWORKS PDM has a file revision counter in the background that is not exposed to the user until it is written to the file data card. Applying the appropriate file revision can be performed by using the ‘Set Revision’ command, or by utilizing a workflow to set the revision at the desired level.

If the only action required on the files is setting the revision, then using the Modify > Set Revision would be appropriate.

Reference the SOLIDWORKS PDM Administration Guide for more information about configuring the prerequisite requirements for the ‘Set Revision’ command to operate correctly.

Should the desire be to adjust more than just the Revision, you may want to consider using an additional workflow to handle these changes. Transitions can have conditions set to detect an existing revision in the custom properties of the files and transition the file appropriately into a Released state with the file vault Revision and data card Revision variable set.

A Workflow link can be used to get the file over to the ‘Rev Set Start’ state for processing:

  1. Troubleshooting Permissions

File permissions consist of two areas that we need to consider when troubleshooting user access and visibility, Folder and State permissions. For simplicity, we are only going to consider only group permissions for Folder and State permissions. More detail about User vs Group based permissions is included in the next section.

Folder and State permissions can be thought of as a breaker and light switch, respectively. The light comes on when both the breaker and the light switch are on. If either one is off, then the light will turn off. In simplistic terms, the same is true for permissions. Allowing the folder ‘Read file contents’ permission will only allow users of the group the ability to see the folders until the same ‘Read file contents’ permission is permitted for the workflow state that the file(s) reside(s) in.

An additional complication with ‘read’ capabilities is the ‘Show Working Versions’ option. If this option is turned off, then the user will only see released versions in the vault. This is a mark set on the files by the ‘Inc. Revision’ workflow transition action.

Should you encounter a permissions issue with access through a workflow, the first place to start is with another user that does have access to the file in question. Use the Version tab of the Windows File Explorer interface to collect the Category, Workflow, Workflow State, Local & Latest Version, and Local (PDM) Revision. Since you can select the file in that location, also record the full folder path to access the file in question.

Use the information collected to access the group that the user is in, then start with Folder permissions. Verify that the group has at a minimum ‘Read File Contents’ enabled. If the file has not been released and the desire is to offer the group read access to interim versions then you will also need to enable ‘Show Working Versions’.

With the Folder permission verified, the next step is to verify Workflow State permissions. Workflow State permissions are accessible from the Workflow or the group, but it is best practice to not administrate one with the other open.

Other problematic permissions are identified and corrected in the same way.

Users & Groups

Users are the backbone of the SOLIDWORKS PDM vault operations. Ensuring proper permissions for the users is vital to their successful operation within the vault. A healthy vault will see that all users are contained within at least one group.

A foundational principle of users and groups is that when permissions are applied to the group, then the permissions will then pass down to the users contained within the group.

There is only one exception to these rules and that applies to the ‘admin’ user. The ‘admin’ user is the super-user in the vault and adding that user to a group may limit the user's access.

  1. Administrating Users?

A common misconception is that users don’t have any rights unless the checkbox is checked in the user’s property manager. If group permissions are applied properly, then the user will receive the rights via the group. That is indicated on the far right anywhere rights can be set:

Beyond adding a user to a group, it is not necessary to apply any of the rights. This will ensure that the user can be added and removed from other groups to assume those rights in a layered fashion, or should a user change departments, then properly applying the new rights can be performed by just adjusting the group that the user is in.

  1. Multi-Group Management

A simple way to view if two or more groups share the same permissions is using the Multi-Group administration dialog. You can get there by right-clicking on Groups > Open. Then you can multi-select with CTRL or SHIFT to then right-click > Properties. This opens the group properties dialog and has both groups loaded for viewing. If permission is unchecked or checked, then that means that all of the selected groups have that setting.

If there are any permissions that one of the selected groups has, but the other doesn’t, then those will show with a green square instead of a check. In this example, Design Engineering has permission to ‘Move Folder’, ‘Add Folder’, and ‘Delete Folder’, but the Engineering department does not. This is why you will see those permissions shown with a green square.

Since these permissions are now using a triple-state view, selecting an option with a green square will enable the option, and clicking it again will turn it off completely. Accepting these changes will apply them to all groups in the original selection and Saving the dialog will commit the changes to the database.

  1. Troubleshooting Permissions

If users have permissions exclusively granted by the groups they are in, then the troubleshooting process is simplified. One of the first steps in the troubleshooting process is to ensure that no user permissions are set and that all of the rights are coming from the groups the user is in. Opening the user and unchecking all left side checkboxes is the first step in ensuring that the user is exclusively using group permissions. Another is to select any dialog tab that starts with ‘Assigned…’, such as ‘Assigned Folder Permissions’. Verify that the window is blank, and if there is an option or folder there, then select and Remove that line.

Should no issues be witnessed in the user, then you will want to look to the groups that the user is contained in and verify that no negation permissions are being applied. In the groups, you will be looking again at the tabs that start with ‘Assigned…’, such as ‘Assigned Folder Permissions’. In this case, folder permission is applied for a top-secret project that the group does not have rights to:

  1. User Removal

When a user is removed from the SOLIDWORKS PDM vault, the history of the user’s interactions with files remains. When an employee is no longer with the company and it is deemed necessary to remove access to the vault, the first step is to take action to check-in all files that the user has checked out. This may mean that the user’s password will need to be changed, so another user or administrator can log in as that person. Then all files can be checked in from the original user’s machine.

The next step is to access the user in the SOLIDWORKS PDM Administration tool to Right-Click > Delete. This will remove access for the user and will also remove the user from the vault. Once completed, the user’s name entry in the database will be updated to include () where the date is the date the user is deleted.

Deleting users who are no longer with the company or no longer need access to the vault will assist PDM Administrators in effectively administrating the remaining users.

  1. Folder Caching

Caching options available in the Group Properties dialog allow for numerous files to ‘sync’ with the user’s system upon login. Effective use of this is vital to efficient login times for users in the group. You will want to include cached locations for folders that contain items like SOLIDWORKS and SOLIDWORKS PDM template files. Another good cached folder is the SOLIDWORKS Toolbox and/or supplier parts area.

Caching performed from the root level of the vault should be used only in extreme circumstances and is not recommended.

Notifications

SOLIDWORKS PDM uses the Message System to transmit relevant document notifications to users. Document notifications consist of change state, delayed in state, and user-triggered (manual) notifications. Other notifications can be set to send when a file action is performed with a single file or from a folder.

  1. Database vs. SMTP*

There are two methods available for the transmission of message data from SOLIDWORKS PDM. The first is by selecting ‘Database’ in the Message System dialog. This method uses the SOLIDWORKS PDM Database Server Service to send messages directly through the system to the user. The message presents in the interface only when the user is logged into the vault. This is the default behavior and no interaction is required for this method to send messages.

The second method available is using SMTP transmission. This method required that you have access to a SMTP (Simple Mail Transmission Protocol) Server or SMTP relay. A relay works to authenticate user credentials with the sending server, such that a trusted source, like the SOLIDWORKS PDM Database server, can transmit a SMTP message to the relay, then the relay securely re-transmits the data to the sending server for transmission out to the user via email.

* SMTP Message Systems are only available with SOLIDWORKS PDM Professional.

  1. SMTP Relays

Many options exist for utilizing a SMTP relay with SOLIDWORKS PDM for sending messages. Historically one of the main reasons a relay is needed is to offer the ability to comply with SSL and TLS security protocols. SOLIDWORKS PDM 2025 now supports and supports SSL and TLS protocols which may bypass the need for a SMTP relay.

Three main options exist for installing and using a SMTP relay. They include using Windows Server, or a third-party software relay. If your company has a relay in place for scanners around the office, that will also work well.

  1. Using Windows Server Relay

This relay method uses IIS on a Windows Server to transmit the SMTP message. Please use this link for more information about the method:

https://support.hostway.com/hc/en-us/articles/360002248059-How-to-Set-Up-An-Internal-SMTP-Service-For-Windows-Server

  1. A Third-Party Relay

This relay method uses a third-party relay that has been used consistently since Solution QA00000114327 was first published in 2012. This is a proxy solution and instructions for the installation are attached to the solution in the SOLIDWORKS Knowledge Base. Here is a link to download the relay software:

http://emailrelay.sourceforge.net/

  1. Missing Email Addresses

The Message System in SOLIDWORKS PDM relies on good email addresses in the users’ properties. If a user’s email is incorrect, it can cause contention and delays in the transmission of messages.

If a user does not have an email address or prefers to receive messages within the system, then you can safely remove the email address from the user. SOLIDWORKS PDM will evaluate that user’s email address as a null value and default back to sending the message through the interface instead.

  1. SQL Monitoring & Troubleshooting

The SOLIDWORKS PDM Database Server Service periodically polls all vault databases and processes notifications, data export rules, and broadcast events. With regard specifically to notifications, they are staged in the DocumentActionInfo table for processing when the query is executed again. The interval in which the query is executed is available by opening the SOLIDWORKS PDM Database Server Configuration tool. The default value is 60 seconds.

Should an issue arise with the message system, restarting the SOLIDWORKS PDM Database Server Service is the first action to take to rectify the issue. Once the service is restarted successfully it will begin processing SMTP messages from the DocumentActionInfo table. When complete, the table will be empty.

A good place to begin troubleshooting the PDM Database Server service can be found in QA00000124884 and QA00000119137. You could also test using a telnet message test, see QA00000118677or QA00000106425. If you prefer using Windows Powershell, troubleshooting steps are in QA00000119354.

Replication

SOLIDWORKS PDM vault replication is a means of bringing archive and/or database data locally to a server near the remote office. This functionality dramatically reduces the user's wait time when accessing data and/or database information.

A great reference for more information is here:

SolidPractices: Setup for Multi-Site Implementations [ QA00000122186]

  1. Scheduling Do’s & Don’ts

Just a few things to keep in mind when scheduling the replication schedules. The target server is setting the interval (time). Meaning, if I have a server in Florida (EST or UTC -05:00) and another in the UK (UTC +01:00). They have a 6 hour time differential.

The best scenario would be to schedule batch replication in both directions after business hours (7 am - 6 pm local time). So that would mean that we would want for the UK transfer to occur at 9:35 pm (21:35) Eastern Time after everyone has left the office with a few hours extra buffer. When putting this time into the Replication Scheme, the time is dependent upon the time of the target server, so you would need to enter ‘35 3 *’. The format is ‘minute hour weekday’, so this reads 03:35 every day. This schedule would start at 03:35 UK time (21:35 US EST). We also set another interval for the UK to US 30 minutes before 21:05 US EST (03:05 am UK).

There is also a reason we want to set the schedule for the top (:05) and bottom (:35) of the hour. When the replication begins, we do not want any other processes happening in the SQL server at that exact moment. This includes backups, other maintenance plans, and other replication queries. We want only the one replication query to occur, process, and then complete before any other action is initiated. Separating the schedules by 5-10 minutes is a good rule of thumb.

  1. Troubleshooting

Replication is an automated process that can be triggered manually to help diagnose issues between servers. There are a few steps that can be taken to help triage and correct the issue.

  1. Network Communications

To get to the root of communication issues between the servers in a replicated vault, you will need to gain Remote Desktop Protocol (RDP) access to all Archive servers. Logging into each Archive server you will want to perform a few tests to verify communications with the other Archive servers. These tests include Ping and Telnet and both can be performed from an elevated Windows Command Prompt.

Examples of Ping and Telnet tests:

Upon pressing Enter on the Telnet command, a blinking cursor in the top left of the command prompt window is a successful result. Any other response will likely return with an actionable error.

As a prerequisite, you will need to install the Telnet Client, which can be done from the Server Manager, by adding Roles and Features in Windows.

Ping and Telnet tests should be performed using the server name when Domain Name System (DNS) translation resolves the Archive Server name to the IP address. Should the name not resolve to the IP address, this may be the issue. Consult with your IT provider to verify that DNS is set up properly to provide proper name translation. Due to the size and scope of Computer Networking, we will not be able to cover all remedies here.

An excellent tool to assist with network communication testing is provided in QA00000119794, and is called the ‘SOLIDWORKS Connectivity Test Tool’.

Cold Storage

Cold Storage can assist you with managing disk space on large SOLIDWORKS PDM file vaults. This can be useful when disk space is not available for allocation to the Archive Server. This function in SOLIDWORKS PDM does not manage database information and should not be considered for database space issues.

Cold Storage can move or delete Archive data from SOLIDWORKS PDM file vaults. Extreme caution should be taken and all other remedies exhausted before considering Cold Storage functionality.

An in-depth look at Cold Storage can be found here:

SolidPractices: Cold Storage [QA00000125791]

As stated in the SolidPractice on Cold Storage, ‘If you select to delete older file versions, the operation is irreversible.’ This means Cold Storage functionality can be extremely detrimental to your vault data if it is used haphazardly. It is best to test all settings used in a non-production environment first, before using them in a production vault.

 

Archive Data Storage

SOLIDWORKS PDM stores archive data in folders on the SOLIDWORKS PDM Archive Server. This location is typically found on the largest data drive on the server. Each time a user makes a change to, and checks in a file, that file data is transferred and stored on the Archive server.

The location of the archive folder on the Archive Server can be found in a few ways. One of these is to access the Archive Server via RDP and open the SOLIDWORKS PDM Archive Server Configuration Tool. Once there, you can expand the archives folder and right-click on the vault(s) to access their Properties. Listed there you will find the path to the main archive folder for the vault:

While rare, it is also possible for Archive data locations to be split across multiple data volumes. To determine if your vault has this occurring, you can inspect the data locations of each of the archive folders by opening the registry on the Archive Server to:

HKEY_LOCAL_MACHINE\\SOFTWARE\\SolidWorks\\Applications\\PDMWorks Enterprise\\ArchiveServer\\Vaults\\[Vault]\\ArchiveTable

In most cases, you will find that your archives reside on the same drive and in the same main archive folder.

  1. Growth Predictions

To best determine the expected growth of a vault, we will want to leverage the database and the history of the vault to best predict the future. This works well if you have been using SOLIDWORKS PDM for a length of time (6+ months). Otherwise, it is best to closely monitor the data usage on the server. A good rule of thumb during the initial setup of SOLIDWORKS PDM is to allocate three times the data expected in the initial migration.

A tool for gaining growth insight has been provided with the following solution:

QA00000110413- Calculate the vault size growth with the Report Generator

In the solution, you will find a report generator query for both deleted and non-deleted files. As stated in the solution, adding the disk space usage values of both reports for the same date range will give the total amount of disk space used during that period.

When the reports are executed, you will be prompted for Start and End Dates for collecting the size information. The image below shows an example result of both of the reports.

This amount can be easily used to extrapolate future vault size growth based on historical data. Simply use the results of the reports divided by the number of months used when prompted by the reports to determine and estimate growth per month moving forward.

(Deleted file space + Active file space) / Months = Data Prediction per month (MB)

  1. Leveraging the Report Generator

To use the growth prediction reports provided in Solution QA00000110413 above, you will need to use the Report Generator. The Report Generator is a tool provided as part of every installation of SOLIDWORKS PDM. You will need to have permission to add reports to the Report Generator, which is found in the group you are in, under Administrative Permissions:

Once the report is loaded, you can offer the report out to other groups in the vault for them to run the reports.

The Report Generator is a function of SOLIDWORKS PDM that leverages T-SQL queries. There are special formatting requirements that can be found in:

QA00000105880- SOLIDWORKS PDM Professional Report Generator tool

Keep in mind that only SQL SELECT statements can be used and are supported by SOLIDWORKS.

 

SQL Performance Tuning

Microsoft SQL Server is the foundation for optimal performance in SOLIDWORKS PDM. If your database(s) aren’t performing optimally, then your users will experience delays with file presentation and in severe cases, extremely long delays for reference lists and other items related to drawings, assembly models, and any other files with large reference trees.

When a user selects a file in SOLIDWORKS PDM or uses the SOLIDWORKS PDM add-in, queries are performed in the database. Depending on the active tab or function selected, this may include a full reference structure query. When the database and instance are optimized, the query can be performed with the lowest possible execution time.

The maintenance schedules and plans found here should be installed and implemented during the initial setup of SOLIDWORKS PDM, or soon after.

  1. Are Backups Needed?

A properly running Microsoft SQL Server without a backup is like driving a Baja 1000 race truck without a spare tire. Database backups are essential for protection against data loss that can completely disrupt business operations.

What that means is creating a plan for backing up all databases created and in use by SOLIDWORKS PDM, so they can be restored on the same or different server. A simple file backup of the .mdf (Microsoft Database File) and .ldf (Log Database File) files is not sufficient for the restoration of the SOLIDWORKS PDM environment. You will need to create a .bak (Backup File), and possibly a .trn (Transaction Log Backup), to restore your SOLIDWORKS PDM databases in the event of a disaster.

  1. Backups in Microsoft SQL Express

Backups for Microsoft SQL Express cannot be automated to occur using the Microsoft SQL Agent, which is a feature available in the Microsoft SQL Standard and Enterprise editions. Instead, you can leverage IT backup software that can perform SQL level backups or you can implement a simple solution with a batch script to perform the backup, and then place that .bat file into a Task in Windows Task Scheduler on the server. See the Microsoft Knowledge Base article KB2019698 “How to schedule and automate backups of SQL Server databases in SQL Server Express” at:

https://support.microsoft.com/en-us/kb/2019698

SOLIDWORKS KB Solution QA00000120028 also offers more information relating to the backup of Microsoft SQL Express databases.

  1. Backups in Microsoft SQL Standard & Enterprise

To perform basic SQL Backups, look in section 10 ‘Backing Up and Restoring File Vaults’ of the SOLIDWORKS PDM Installation Guide:

https://files.solidworks.com/Supportfiles/PDMWorks_Ent_Installation/2025/English/Installation%20Guide.pdf

The methods outlined in the SOLIDWORKS PDM Installation Guide will achieve what is needed for basic backups, especially for databases that are set to use ‘Simple’ as the Recovery Model. However, this would not be optimal for a database that is set to use ‘Full’ as the Recovery Model, which is the default. In this case, transaction log backups should also be performed regularly to help reduce the size of the .ldf file. For optimal performance, the total size of the .mdf and .ldf files combined must be smaller than the size of available RAM on the server, while reserving enough for Windows and other Windows-related processes (approx. 4 Gb). This way you ensure that Microsoft SQL Server can execute all operations in RAM and is not forced to read and write to disc, which can be considerably slower.

When performing a transaction log backup, you will follow the same procedure as a database backup, except for changing the Backup Type to be ‘Transaction Log’ and verifying that the file name that is written out includes .trn as the file extension.

These two recovery models also offer different Work Loss Exposure in the event of a disaster. When using a Simple recovery model, you could potentially lose all the changes since the last backup occurred. With a Full recovery model, the risk is lower, but the transaction log backups will need to occur more frequently to ensure their size remains in check.

If the tail of the log is damaged, changes since the most recent log backup will be lost.

Traditionally, DBAs will use a Full recovery model with very frequent transaction log backups. This model works well for web applications and other database applications but is not necessary for SOLIDWORKS PDM. We recommend that you set your database recovery model to ‘Simple’. The reasoning for this is that should a disaster strike, you will need to use a backup of the database that is as close to the archive backup time as possible. If you are only backing up the archives once per day, then a more frequent database backup is not helpful and unnecessary. The best model is to backup the databases a few minutes before the backup of the archive backup from the server so your backup will contain a matched pair for restoration.

More information about the Recovery Models is available here:

Full - https://www.mssqltips.com/sqlservertutorial/3/sql-server-full-recovery-model/

Simple - https://www.mssqltips.com/sqlservertutorial/4/sql-server-simple-recovery-model/

https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/recovery-models-sql-server?view=sql-server-ver15

  1. Database Table Index Fragmentation

For your PDM Vault to perform at the highest level, you will want your table indexes to not be overly fragmented. Fragmentation occurs when data is written out of sequence, through multiple inserts, update, and delete transactions in the table. These activities cause the physical order on the disk for the index to be out of sequence from the logical order of the data (as defined by the index key). Slower performance may occur when these index pages are dispersed across non-adjacent sectors on the physical disc.

You can think of the indexing concept as a perfectly alphabetized book collection, so finding the desired book by title is very fast. When fragmentation occurs, it is similar to removing books from the collection for reading and then returning them. The only catch is, they can only be returned to the end of the index, like using a librarian cart for instance. Hence the gaps left and the out-of-sequence order is the fragmentation that occurs. This example is over-simplified as in addition to a book title index, we may also have an index for the author name, the number of pages, or any other important data point. Each of these indices is organized and sorted for optimal performance with a different primary reference for sorting.

Maintenance tasks such as Rebuild and Reorganize can assist with optimizing these table indices for faster table queries, such as search, where used, contains, BOM, check-in/out, and others. In addition to reducing seek time for queries, these tasks can also assist with reducing the drive space consumed by the indices.

For more information about using the Status Reporting Tool to locate fragmented table indices, reference QA00000123510.

  1. Maintenance Scheduling

Microsoft SQL Server Standard and Enterprise editions come with the ability to leverage the SQL Server Agent. The SQL Server Agent’s role is to execute scheduled administrative tasks, which are called jobs in SQL Server.

Maintenance Plan tasks include:

  • Back-Up Database Task
    • This task allows you to perform full, differential, files and filegroups, and transaction log backups.

• Rebuild Index Task

  • This task allows you to re-create the indexes on the tables in the database.

• Reorganize Index Task

  • This task will move index pages into a more efficient search order.

• History Cleanup Task

  • This task allows you to delete backup and restore history, SQL Server Agent Job history, and maintenance plan history

• Maintenance Cleanup Task

  • Use this task to remove old files related to maintenance plans, including text reports created by maintenance plans and database backup files

Maintenance Plans are recommended for the following schedule:

• Daily – Perform backup of databases using the ‘Full’ backup type

  • If the recovery model is set to Full, then you will also need an additional maintenance plan for Transaction Log backups.

• Weekly – Tasks will be added to perform Reorganization and Rebuilding of database indices.

  • This guideline is a great starting point, but you will need to monitor fragmentation in the indices and adjust frequency based on the results. Reference QA00000123510 for using the Status Reporting Tool to locate fragmented table indices.

• Monthly – Once a month, a task will run to Update Statistics and perform History & Maintenance Cleanup

• Quarterly or as required – Test the backups!

Note: Maintenance Cleanup can be performed along with any of these plans. The frequency in which cleanup of old backup files depends on your company’s retention policies.

A more detailed description and deep dive on maintenance plans can be found in section 3.k.i in:

SolidPractices: SQL Server Performance [QA00000123510]

  1. Database and Instance Optimization

Microsoft SQL offers several options for investigating the source of issues, but the best way to avoid needing these is to optimize your databases during the initial implementation, or as quickly as possible after.

Microsoft SQL 2019 has vastly improved the way that settings are determined and optimized during installation. Items like recommended RAM settings, to operate with optimal parallelism and core count are all now covered during the setup of Microsoft SQL Server 2019.

During the installation, in the Database Engine Configuration section, you will want to review both the MaxDOP and Memory tabs.

  • MaxDOP – The option sets the SQLMAXDOP setting based on the number of cores found on the machine when performing the installation.
  • Memory – The recommendation is to use the Recommended setting which will leave memory available for the proper operation of Windows Server. Further adjustments can be made to this, but the default setting does set the memory allocation to the proper range based on the machine’s installed RAM.

Conversely, using the Default setting is approx. 2.15 Petabytes. SQL can consume all of the RAM on the server if you do not have more than 2.15 Petabytes of RAM, and the performance of Windows operations will be degraded.

MaxDOP

 

Memory

 

For an exhaustive list of recommended settings and a more exhaustive document dedicated exclusively to the performance of your databases for SOLIDWORKS PDM, called SolidPractices: SQL Server Performance [QA00000123510]

Installation and Upgrades

A solid and consistent installation of SOLIDWORKS products is crucial to ensure optimal performance for the end-user. It is possible to install SOLIDWORKS products as standalone installations, SOLIDWORKS Image deployments, or using 3rd Party tools. The same consistency can be applied using all three methods, but the later methods offer more automation than using a standalone installation. Upgrading systems to later versions is equally important.

All tips and tricks in this are highlights and additions to the SOLIDWORKS Installation and Administration Guides found here:

https://my.solidworks.com/support/adminguides

Two fantastic references when it comes to upgrades are:

SolidPractices: SOLIDWORKS Upgrades [ QA00000122088]

SolidPractices: Managing SOLIDWORKS PDM Upgrades [QA00000125635]

  1. Push Installs for Clients

With automatic deployment, installation tasks are pushed to target machines and carried out by the Microsoft Task Scheduler on each system, without requiring any actions by users. Use this method when users do not have administrative privileges to install software on their systems.

With a push installation, the Task Scheduler launches SOLIDWORKS Installation Manager to run under credentials specified by you, the administrator. The Task Scheduler runs under the computer’s LocalSystem account. This account is represented on the network as a computer security principle. The computer security principle must have read access to the shared folder where the administrative image is located, and write access to the ‘x64\\logs’ folder.

In Active Directory, when you add a computer to a group of a shared folder, select Object Types and make sure that Computers is selected. In addition, the computer serving the administrative image and the target client machines must be members of the same Active Directory domain.

To perform the Automatic Deployment, use the following steps:

  1. Select Deploy Automatically in the Option Editor
  2. Select the machines/groups you wish to deploy
  3. Set the option on the right for the deployment
  1. Use the Test button to verify that the clients will deploy
  2. Should the Test fail, hovering over the red X will offer some guidance
  1. Before deploying the image in production, all tests will need to be successful, use the Test and Run Again options until all issues are resolved.

 

  1. When ready, click Deploy

 

  1. Verify the network path
  2. Click OK
  3. Status Column will show completed installations

Security software and firewalls can also be a concern when running push deployments. You will need to ensure and test in your environment, to ensure that there are no issues in your test machines before full-scale deployment.

Other 3rd Party tools such as Microsoft Software Center (SCCM) can be used for the deployment instead of the SOLIDWORKS deployment method. Due to the sheer size of the installation, it can be cumbersome when deploying to remote sites and VPN users. For these types of environments, a localized copy of the network installation files offers a high success rate. Many applications can be packaged up into SCCM as a full package, but this is not advised for SOLIDWORKS installations. Instead, a series of scripts can be used to accomplish this.

The scripts will be used to:

  • Initiate prerequisite installations
  • Local caching of the administrative image
  • Utilization of file syncing software or a simple Robocopy script can be used to accomplish this task. The script can look like the one below, but you will need to verify that the appropriate triggers are used for proper execution in your environment:

    robocopy.exe "\\\\Server\\SOLIDWORKS 20XX SPX" "C:\\SolidWorks\\20XX" *.* /e /dcopy:t /r:5 /w:5 /tee /mt

 

  • Execution of the local administrative image
  • Application of settings and other registry tasks
  • Installation of secondary items like distributed vault views

Refer to the Command-Line Deployment section of the SOLIDWORKS Installation Guide for additional information about the commands needed:

https://files.solidworks.com/Supportfiles/SW_Installation_Guide/2022/English/install_guide.pdf

  1. Distributed Vault Views

The installation of SOLIDWORKS PDM is just part of the procedure for getting a user access to the vault. You will also need to apply a vault view to the machine for the user.

Detailed step-by-step instructions for creating a distributed vault view setup file can be found in section 7 of the SOLIDWORKS PDM/Manage Installation Guide.

To further automate the installation of the vault view you can leverage a command-line string for applying the vault view with ViewSetup.exe and a previously created .cvs file. The command can be run silently using a quiet flag (/q) on the end:

ViewSetup.exe PDMWEVault.cvs /q
  1. Server Moves

When moving a server or upgrading it may be necessary to re-point the client’s local vault view. This method should only be used after all files have been checked in from the vault view, before the move.

<strong>IMPORTANT: The potential for harm to your machine is very high when editing the registry in Windows. If you do not feel comfortable with making changes to the machine using the registry, then the alternative is deleting and re-attaching the vault view through the GUI interface.</strong>
<strong>Details on re-attaching the vault view can be found in the </strong><a href="https://files.solidworks.com/Supportfiles/SW_Installation_Guide/2027/English/install_guide.pdf" rel="nofollow"><strong>SOLIDWORKS PDM Installation Guide</strong></a><a href="https://files.solidworks.com/Supportfiles/SW_Installation_Guide/2022/English/install_guide.pdf" rel="nofollow"><strong>.</strong></a>

For vault views that were installed with all users method, the vault view uses two registry keys that point the workstation to the archive server. ‘ServerLoc’ and ‘DbServer’ can be found in the following locations:

<i>HKEY_LOCAL_MACHINE\\SOFTWARE\\SolidWorks\\Applications\\PDMWorks Enterprise\\Databases\\vaultname</i>

and

<i>HKEY_LOCAL_MACHINE\\SOFTWARE\\WOW6432Node\\SolidWorks\\Applications\\PDMWorks Enterprise\\Databases\\vaultname</i>

For private vault views, the vault view’s ‘ServerLoc’ and ‘DbServer’ can be found in the following location:

<i>HKEY_CURRENT_USER\\Software\\Solidworks\\Applications\\PDMWorks Enterprise\\Vaults\\vaultname</i>

Automating the change of these keys can be performed using command line scripting or group policy updates. When performing any update to the registry, it is very important to back up the machine and to export the existing registry before making any changes.

Further information about moving servers can be found in the ‘Moving Server Components to Another System’ section of the SOLIDWORKS PDM/Manage Installation Guide.

 

Server & Workstation Upgrades

SOLIDWORKS, SOLIDWORKS PDM, and the SOLIDWORKS SolidNetwork License (SNL) Manager Server can all be upgraded independently, or together when new releases and service packs come out. As these products continue to improve, you will need to upgrade your servers and workstations to fully realize these changes.

While it is possible to upgrade any of the SOLIDWORKS products independently, it is best to upgrade SOLIDWORKS and SOLIDWORKS PDM together. Should it not be possible to upgrade SOLIDWORKS and SOLIDWORKS PDM together in your environment, then it is best to upgrade SOLIDWORKS PDM ahead of SOLIDWORKS. SOLIDWORKS PDM does understand the file format and if SOLIDWORKS is newer, you may receive an error regarding the file format not being recognized.

The SNL Manager server can be upgraded independently and will serve out licenses to older versions of SOLIDWORKS products, but not newer ones. That means that the SNL Manager will need to be upgraded first if you are considering a staged upgrade process.

  1. System Requirement Gotchas

Any time an upgrade is considered, there are several items to verify before upgrading. You will want to verify that your Windows Server OS is at or newer than the minimum required version. You will also want to check that you have the required level of Microsoft SQL Server. In most cases, the cumulative update (CU) will need to be applied.

The minimum system requirements are listed here:

https://www.solidworks.com/support/system-requirements

On the system requirements page you will be able to verify that you are using the proper versions of the following for your servers and workstations:

  • Operating Systems
  • Microsoft SQL & Microsoft Office
  • Hardware & Hypervisors
  • Antivirus
  • Support Lifecycle
  1. VAR Services

When it comes to upgrades, your Value Added Reseller (VAR) can be an invaluable asset. They will be able to help guide you through the upgrade process so your next upgrade is performed with great efficiency. Many of the techniques shared here are deployed by your VAR regularly, so they are already familiar with the items to watch out for and tasks to avoid during the upgrade.

 

File Version Upgrades

The SOLIDWORKS PDM File Version Upgrade Tool (FVUT) is a utility that is part of the installation, which assists with upgrading the file version of SOLIDWORKS files. The file format improvements and performance enhancements can be realized year after year by leveraging the FVUT after you upgrade SOLIDWORKS and SOLIDWORKS PDM.

Older version SOLIDWORKS files may say that they are not rebuilt, and the easiest way to correct this issue, especially on already released files, is to run the FVUT. The tool will open, convert and save SOLIDWORKS files from the vault and will also likely improve the performance of SOLIDWORKS in the process.

More information about setting up and performing a file version upgrade can be found here:

SolidPractices: File Version Upgrade Tool [QA00000124438]

It is always best to test in a non-production environment, that way you can get the correct settings for your environment, before running them in the production environment.

Comments 0