Server Considerations: Selecting the Right Hardware for SOLIDWORKS PDM

At its core, SOLIDWORKS PDM is a ‘traditional’ Client / Server application designed to be installed on one or more Windows Server(s) within a Local (LAN) or Wide Area Network (WAN), and the purpose of this article is to address the questions we are typically asked regarding hardware selection.

Components of SOLIDWORKS PDM

Before we discuss those questions, lets first consider the architecture of SOLIDWORKS PDM and a few deployment scenarios.

To use SOLIDWORKS PDM, the following components must be installed and configured. For an explanation of terminology used within this article please refer to the appendix. For up-to-date information on supported environments please refer to the SOLIDWORKS website.

The following (SOLIDWORKS PDM Professional) installation components are optional

For the majority of our customers, who have a single site deployment of SOLIDWORKS PDM, a single Server will be deployed to host all PDM Components. For optimal resource planning in medium to large PDM deployments however, it is sometimes beneficial to separate the Archive and Database Server Services to their own dedicated servers. For a multi-site deployment additional archive, and optionally database, servers may be required.

Scenario 1: PDM Standard or Professional | Single site

The diagram (below) illustrates a ‘typical’ small to medium sized installation of SOLIDWORKS PDM STANDARD or PROFESSIONAL within a single LAN.

In this scenario, one server runs all PDM software and services. SOLIDWORKS PDM client PC’s attach to the server within the local network over a Windows domain or workgroup.

Scenario 2: PDM Professional | Single Site with Remote (web) Users

This next diagram (below) illustrates an example of a large, single site, installation of PDM Professional with remote contributor or viewer access via the Web.

In this scenario we have multiple servers; One server running Microsoft SQL Server hosts the file vault database(s) and the Database Server Service and a separate server hosts the Archive Server Service, and SolidNetwork License Manager (SNL). Workstations installed with the SOLIDWORKS PDM client attach to the servers within the LAN and a Web server, outside the company firewall, allows access to PDM using SOLIDWORKS PDM Web clients.

Scenario 3: PDM Professional | Multisite

This third scenario shows the previous PDM Pro deployment with the addition of a remote connected site, running a replicated Archive Server that the clients on that site are connected to, and optionally also taking licenses from (requires a separate serial number).

NOTE: In this scenario whilst files are added to and taken from a local ‘Archive’, the users on the remote site are still connected, via the WAN, to the database server on the primary site.

A fourth (not illustrated) scenario could include a replicated (Read only) database on the remote site too. This is rarely deployed however, due to the requirement for SQL Server Enterprise to support this set up.

Do I need dedicated hardware for SOLIDWORKS PDM?

As indicated above, for optimal resource planning and flexibility, it is recommended to have SOLIDWORKS PDM on its own dedicated Server, and for medium to large PDM deployments, it may be beneficial to separate the Archive and Database Servers to their own dedicated platforms.

Database Server Service: For best performance it is best to install the SOLIDWORKS PDM Database (DB) Server Service on the same system as the SQL Server software. If your DB Administrators do not permit this, it can be installed alongside the Archive Server, but this introduces a small risk of DB timeouts because of the increased latency.

Other databases: To allow for discrete tuning and maintenance, we advise that you don’t host other databases on the same SQL Instance as the PDM database.

In summary, while it is possible to run SOLIDWORKS PDM on shared hardware for smaller setups, using dedicated hardware is recommended to ensure optimal performance and reliability.

Can I install SOLIDWORKS PDM on a PC?

Whilst Dassault Systèmes SOLIDWORKS no longer actively state that running SOLIDWORKS PDM server components on a PC is unsupported, installing server software on a PC is generally not recommended for several reasons:

1. 1. Uptime and Reliability: Servers are designed to run 24/7 with minimal downtime, whereas PCs are not built for continuous operation. This can lead to increased risk of hardware failure and data loss.
   2. Security: Servers often have advanced security features that are not available on standard PCs. These features are crucial for protecting sensitive data and ensuring secure access.
   3. Hardware Limitations: PCs typically lack the redundant power supplies, error-correcting memory, and other hardware features that are standard in servers. These features are essential for maintaining data integrity and system stability. Servers are also designed to be scalable, allowing for easy upgrades and expansion as the needs of the organization grow. PCs, on the other hand, have limited scalability.
   4. Network Performance:

Servers are optimized for handling high network traffic and multiple connections simultaneously. PCs may struggle with network performance under heavy loads, leading to slower response times and potential bottlenecks.

In summary, while it is technically possible to install SOLIDWORKS PDM Server software on a PC, it is not advisable due to performance, security, scalability, and reliability concerns.

Can I install SOLIDWORKS PDM on a Domain Controller?

Although SQL Server can operate on a domain controller, it is not advisable for optimal performance. To achieve the best results, SQL Server (and therefore PDM) should be hosted on a dedicated server rather than one that performs multiple functions, such as a domain controller or file server.

Managing servers that support multiple applications presents challenges, as each application may demand distinct and sometimes incompatible configurations. Whilst no longer blocked by the Installer, Microsoft does not recommend installing SQL Server on a domain controller because of security and performance concerns:

Security

Domain controllers represent prime targets for potential attackers, and installing PDM on them could expose critical IP stored within the vault, potentially leading to network-wide security breaches. Moreover, installing additional software on domain controllers elevates the risk of potential vulnerabilities.

Performance

For best performance, SQL Server should be dedicated to its own server and not shared with other functions. It can be difficult to tune servers that run multiple applications and left unrestricted, SQL Server has the potential to grab all the resources from the OS ad other functions, which could effectively shut down your domain controller and, in turn, your network.

Complexity and Maintenance:

Integrating PDM with domain controllers can complicate system maintenance and upgrades, necessitating careful coordination to ensure compatibility and minimize downtime. Technical support may be reluctant to modify registry files or reboot servers during operational hours, potentially disrupting critical services.

SQL Specific Limitations

There are several limitations that apply when installing SQL Server on a domain controller, including:

• You can’t run SQL Server services using a local service account.
• You can’t change the computer from a domain member to a domain controller without uninstalling SQL Server first.
• SQL Server failover cluster instances aren’t supported if cluster nodes are domain controllers.
• SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.

In conclusion, whilst technically feasible, installing PDM on a domain controller is fraught with risks that could compromise both security and performance. Organisations are urged therefore to adhere to best practices and explore alternative deployment strategies to ensure seamless operations while safeguarding critical data.

One option could be to utilise virtual server instances for Domain Controllers and deploy PDM in separate instances on the same virtualised server.

Are Virtual or Physical Servers best for SOLIDWORKS PDM?

In many cases, the simplicity of a dedicated physical server, with potentially lower upfront costs and ‘hands on’ maintenance, may be a better option for smaller organisations implementing PDM and Solid Solutions are able to provide suitable hardware (tower and rack) via our partnership with Dell. For larger organisations where virtualisation already has a foothold, it is likely you will want to continue with that strategy for PDM. But does SOLIDWORKS PDM work in virtual environments? In simple terms… Yes, however SOLIDWORKS only test, and therefore support, PDM in specific virtual environments with some Hypervisors actively blocked due to risks around software compliance.

To see the latest supported version of a specific virtualisation platform for the version of PDM you are deploying, make sure to check the system requirements page.

What are benefits of virtualisation?

Cost savings: Virtualisation can reduce the number of physical servers required, which can lower the overall cost of hardware and therefore also has the chance to potentially reduce energy costs.

Improved efficiency: Virtualisation can help IT teams be more productive by reducing the time spent maintaining physical hardware. Remote management of Virtual Machines is also greatly simplified as the platforms are developed specifically to support this.

Better scalability: Virtualisation allows for on-demand scaling, so you can easily increase or decrease the number of virtual machines, or the allocated resources / storage capability to specific machines based on your changing needs.

Safer application testing: Virtualisation can be used to quickly deploy pilot environments to test new releases or functionality without affecting production.

Improved disaster recovery: Virtual machines can be cloned or replicated to help with disaster recovery.

Can I install SOLIDWORKS PDM on ‘The Cloud’?

Interest in cloud-based data management solutions has risen significantly in the last few years. For current SOLIDWORKS PDM users – and those looking to implement a PDM solution for the first time – you may be wondering, can SOLIDWORKS PDM be hosted in the cloud? And the answer is yes!*

SOLIDWORKS PDM can* be hosted “in the cloud” which means that the server components of PDM are installed on a Virtual Machine in a private datacentre or commercial cloud computing service like IoMART, Amazon Web Services or Microsoft Azure.

Your team then connects to the virtual server via the internet, allowing access to your PDM Vault in the same way they would connect to a server if it were physically located in your office. Whether your SOLIDWORKS PDM is installed on a local or cloud hosted server, the end-user experience is the same.

Users can check files out/in to the vault, track revisions, and manage approval processes with all of the same functionality, and all within Windows File Explorer.

When implementing SOLIDWORKS PDM on-cloud (as shown), one or more virtual machine(s) are used to host all the PDM Server components, such as the database, archive and SNL much like the previously discussed deployment scenarios. However, rather than using a local server that physically sits in the office, the server is in a data centre.

In the UK, Solid Solutions Partner with iOmart to offer a complete cloud hosted solution covering installation, implementation and maintenance. In North America TriMech utilise both Amazon Web Services (AWS) and MS Azure.

iOmart are a UK based company that provided managed hosted environments. They have various datacentres in the UK and footprints around the world. They are highly accredited and a certified Microsoft partner.

We have partnered with iOmart for a number of years now and they provide hosting solutions for Windows VMs that have been specified specifically to support SOLIDWORKS PDM. iOmart take care of the uptime and manage the Servers on their platform infrastructure as well as supporting the networking for customer connectivity and firewall configuration. They are also able to supply SQL Standard licenses for PDM Professional deployments using both core and user/device licensing models.

Our iOmart infrastructure is safe and secure with each of our customers having their own dedicated virtual server and network subnet. The internal firewalls taking care of restricting access between VMs to ensure customer environments are fully secure.

Depending on where you host there are different configurations available for connecting to the cloud server, but a common one is shown in the diagram above where the virtual server is connected directly to the local network (site to site VPN), so that any users who connect to the LAN automatically have access to the cloud server. For remote users, their personal VPN connection can also go directly to the cloud hosted PDM server.

As Cloud Hosted Servers are also vrtual, by installing your PDM in the Cloud you get all the benefits of virtualisation with several added benefits.

#1 – Cost

With a traditional on-premises setup, the server where PDM resides must undergo regular upgrades and maintenance.

Every so often, the hardware may even become obsolete requiring an entirely new machine be purchased. Plus, managing the server and its connection to the users typically requires an IT resource.

When using a virtual machine, your server is managed and maintained at an industry-leading datacentre, over time, the costs of maintaining physical servers on-premises may prove to be more expensive than a monthly recurring fee for the virtual server.

#2 – Security

Storing your data at a remote location means you have an extra layer of security from events that may cause problems for an on-premises PDM server, such as power outages, fires, floods, or other events beyond your control.

With your data secured in a virtual server, you’ll never have to worry about downtime if your office becomes inaccessible.

By storing data in a virtual environment such as SOLIDWORKS PDM Standard, it is also safe from things like physical damage or overheating, which may occur to an in-office server if the proper precautions are not taken.

#3 – Remote Working Flexibility

For users who often work remotely, connecting to the office network via VPN means their connection speed is limited by both internet speeds (Home and Office) and the LAN saturation at the office.

This means if the office network has a slow internet connection or is experiencing particularly high bandwidth usage onsite, the remote user will also be impacted by that slowdown.

However, when a user is connected to the cloud server, they will be connecting directly to the datacentre, and are essentially only limited by their home/office internet speed.

If you are investigating your own cloud environment, please take note of the following:

• Azure Managed Instance and Azure SQL are not supported by SOLIDWORKS PDM meaning you need to install full SQL Server on the Azure Server.
• Amazon Web Service’s Relational Database Services (RDS) is not an appropriate option for hosting PDM databases as it does not allow using a db owner This leads to several issues when using PDM.
• The latency between the clients to the cloud server must be under 150 milliseconds to prevent issues, best performance will be achieved if latency is below 100 milliseconds. Keep this in mind when selecting your availability zone.

What are the recommended Hardware specifications for a SOLIDWORKS PDM server?

The following recommendations are for a ‘good’ server, not the minimum requirements.

• All drives are SSD, with RAID 1 recommended as a minimum for SQL drive(s) and if possible, RAID 10 for ultimate performance and resilience on DATA drives.
• For operating system / SQL Server version support please refer to system requirements
• For the Database Server, Microsoft SQL can take advantage of multi core processing. For optimal performance of PDM functions, it is recommended that the average CPU utilization be kept below 50%. If average utilization is above 50%, then more cores may be needed.Please note, If using Microsoft SQL Server Standard Core Licensing, adding additional cores may require also purchasing additional core licenses. The 4 Core recommendations below is based on minimum SQL Core based licensing requirements.

PDM Standard Combined SQL and Archive Server

• Processor: x64 bit Intel or AMD Processor: For virtual servers we would suggest 2.5Ghz and above. For a physical server with only 4 cores then 3Ghz or higher may be more suitable.
• Memory: 16 Gb RAM (8Gb minimum)
• Storage configuration: Drive 1: 150 Gb (for OS and SQL), Drive 2: 500 Gb (Min) for Archive

PDM Professional Combined SQL and Archive Server

• Processor: x64 bit Intel or AMD Processor: For virtual servers we would suggest 2.5Ghz and above. For a physical server with only 4 cores then 3Ghz or higher may be more suitable.
• Memory: 32 Gb RAM (16Gb minimum)
• Storage configuration: Drive 1: 150 Gb (for OS and SQL), Drive 2: 500 Gb (Min) for Archive

PDM Professional Separate SQL and Archive Server

SQL Database Server:

• • Processor: x64 bit Intel or AMD Processor: For virtual servers we would suggest 2.5Ghz and above. For a physical server with only 4 cores then 3Ghz or higher may be more suitable.
  • Memory: 16 Gb RAM (16Gb minimum)
  • Storage configuration: Drive 1: 150 Gb (for OS), Drive 2: 150 Gb (SQL)

Archive Server:

• Processor: x64 bit Intel or AMD Processor: For virtual servers we would suggest 2.5Ghz and above. For a physical server with only 4 cores then 3Ghz or higher may be more suitable.
• Memory: 16GB
• Storage configuration: Drive 1: 150 Gb (for OS), Drive 2: 500 Gb (Data – minimum)

Summary

In closing. When selecting hardware for SOLIDWORKS PDM, advice is generally based around the following key considerations:

1. Scalability: It is inevitable, since PDM stores all historical versions of your files, that moving your data into PDM will over time increase your storage needs. So, as your data grows, your hardware should be able to handle increased storage and processing requirements. How you scale will depend on whether your server is physical or virtual but ensuring that your hardware can scale with your business needs is paramount.

   Please Note: Whilst it is typical for the PDM File Archive to sit within a single ‘Drive’, SOLIDWORKS PDM does support ‘Archive Distribution’ to allow you to split the archive over multiple drives.

   However, as SOLIDWORKS do not currently support the use of network attached storage for PDM you should plan for expansion based on only adding ‘internal’ storage to your physical or virtual server.

2. Performance: Choose hardware that offers high performance to manage large datasets efficiently. For database performance, this includes fast processors and ample RAM. For the Archive Server high-speed and resilient storage solutions is also advisable.
3. Reliability: There could be millions of pounds worth of intellectual property on that server so always opt for reliable hardware with redundancy features to minimize downtime and data loss. With physical servers, this includes RAID configurations for storage, backup power supplies and a comprehensive disaster recovery plan. For virtual / cloud Servers mirrored servers, and backups should be part of the contract.
4. Compatibility: If investing in a new hardware platform, ensure it is compatible with your PDM software and other systems in your IT infrastructure for as long as possible.
5. Security: Implement hardware that supports robust security measures to protect sensitive product data from unauthorized access and cyber threats and ensure that operating system and other security patches are applied as soon as possible.These considerations help ensure that your PDM system runs smoothly and supports your business’s productivity and growth.

Terminology

It’s fair to say that this blog is full of technical language. For clarity, we’ve provided a glossary of technical jargon below!