SOLIDWORKS PDM Server Infrastructure Guide

Server infrastructure for SOLIDWORKS PDM is a topic that deserves more than a spec table and a footnote. Most guides offer a minimum requirements list and leave the reader to fill in the gaps. That works if you are installing a test vault. It doesn’t work if you are deploying PDM for a team of engineers who will depend on it daily, or if you are trying to understand why a system that was correctly specified three years ago now feels unreliable.

The decisions around physical vs virtual infrastructure, SQL version, licensing model, CAL structure, and storage architecture all interact, and getting one right while overlooking another is often the root cause of performance problems that get misdiagnosed for months. This guide examines each factor properly, so the decisions you make are grounded in understanding rather than assumption.

Choosing the right server infrastructure for SOLIDWORKS PDM isn’t simply a hardware decision, it’s a systems engineering one. Get it right and users barely notice the server exists. Get it wrong and the symptoms are subtle at first – small delays, inconsistent responses, workflows that feel sticky. Over time, those friction points erode trust in the system entirely.

This guide covers infrastructure requirements for PDM Standard, PDM Professional, and PDM Manage across physical, virtual, and cloud environments, including the server software, SQL licensing, and Client Access Licenses (CALs) you’ll need to budget for alongside the hardware.

Physical vs Virtual Infrastructure

SOLIDWORKS PDM can be deployed on both physical servers and virtual machines. Both are valid when correctly engineered, but behave differently under load.

• Physical servers deliver the most consistent and predictable performance
• Virtual servers offer flexibility and scalability, but depend heavily on resource allocation and latency control

For most engineering environments, physical infrastructure remains the preferred baseline. Virtual deployments are increasingly viable in cloud or hybrid strategies — provided latency and resource design are managed carefully.

In our deployments across the UK and Ireland, the majority of smaller engineering teams opt for physical servers for simplicity and predictability. Virtualisation tends to come into the conversation when an organisation already has a managed virtual environment and wants to bring PDM into it — which is entirely reasonable, provided the conditions are right.

PDM Standard

PDM Standard is designed for smaller teams with straightforward workflows. It’s a SQL-driven transactional system so the server specification matters.

We often see PDM Standard treated as a lightweight product that will run comfortably on any spare hardware. This assumption causes problems. The SQL Express limitations in particular, especially the 1GB memory cap, mean that even a small team on underpowered hardware will start to notice performance degradation sooner than they expect.

Suited to:

• 1–10 users
• Small vaults and simple workflows
• Single-site environments

Physical Server (Recommended)

Virtual Machine (Conditional Use)*

* Virtual environments at this tier require consistent latency (ideally under 20ms), no CPU oversubscription, and high-performance storage. Meet those conditions and a VM works well. Miss them and even a small PDM deployment will feel sluggish.

Server Software – PDM Standard

PDM Standard installs its own archive server and database server components. The database is hosted on Microsoft SQL Server Express, which is bundled with PDM Standard at no additional cost.

SQL Express is free for commercial use but carries meaningful limitations that are worth understanding:

The 10GB database limit is rarely a concern in practice for small PDM Standard vaults. The 1GB memory cap is more significant as everything in PDM flows through the database, and restricting SQL memory directly constrains how many concurrent users the system can serve reliably.

Windows Server CALs

Every user or device connecting to the PDM server over a Windows Server OS requires a Windows Server Client Access Licence. These are purchased separately from Microsoft and are a legal compliance requirement regardless of which PDM tier you are running. Your IT team or Microsoft reseller can advise on the right quantity and model (User CAL vs Device CAL) for your environment.

SQL CALs for PDM Standard

Not required — SQL Express does not use the CAL licensing model.

What Does a PDM Standard Server Cost?

Prices below are indicative UK figures based on current market pricing (June 2026). Hardware costs vary by configuration and supplier — treat these as realistic planning figures rather than fixed quotes.

All prices shown exclude VAT. Hardware prices are one-off purchase costs. Cloud figures are monthly recurring.

Physical server (outright purchase)

SQL Express is bundled with PDM Standard and PDM Standard does not require SQL CALs or Windows Server CALs — there is no additional licensing cost at this tier beyond the OS itself.

Cloud VM — Microsoft Azure (monthly recurring)

Azure VM costs above cover compute only. Storage (Premium SSD), Windows Server licensing (if not using Azure Hybrid Benefit), and backup should be added to arrive at a true monthly total — typically £180–£250/month all-in for a small PDM Standard cloud deployment.

PDM Professional

PDM Professional introduces higher concurrency, larger vaults, and more complex workflows. The demands on SQL and storage increase accordingly, and the consequences of under-specification become more visible.

This is the tier where we do the most infrastructure consultancy work. Teams moving from Standard to Professional sometimes assume the jump is primarily a software licensing decision. In reality, the infrastructure requirements alos change significantly, particularly around SQL, where you move from a free, capped Express instance to a licensed Standard or Enterprise deployment that needs to be correctly sized from day one.

Small Teams (1–10 users)

Physical Server (Recommended)

Virtual Machine (Conditional Use)*

*At this scale a VM is viable, but the conditions are stricter than PDM Standard. SQL Server Standard will use available RAM aggressively to cache the database — ensure RAM allocation is dedicated, not shared with other VMs on the host. Latency under 20ms between VM and client workstations is the practical threshold for acceptable performance.

What Does a PDM Professional Server Cost? (1–10 users)

All prices shown exclude VAT. Hardware costs are one-off purchase costs. Cloud figures are monthly recurring. SQL licensing costs are covered separately in the SQL Licensing section below.

Physical server (outright purchase)

Cloud VM — Microsoft Azure (monthly recurring)

Add Premium SSD storage, Windows Server licensing, and backup for a realistic all-in monthly figure of approximately £200–£300/month. SQL Server licensing is a separate cost on top of this regardless of deployment type.

Growing Teams (10–25 users)

Physical Server (Recommended)

Virtual Machine (Conditional Use)*

*At this user count, VM performance becomes more sensitive to host configuration. CPU oversubscription on the hypervisor host is the most common cause of PDM performance problems in virtualised environments at this scale. If the host is running multiple demanding VMs, dedicated physical resource allocation for the PDM VM is essential rather than optional.

What Does a PDM Professional Server Cost? (10–25 users)

All prices shown exclude VAT.

Physical server (outright purchase)

Cloud VM — Microsoft Azure (monthly recurring)

All-in monthly cost including Premium SSD storage, Windows Server, and backup: approximately £380–£500/month. SQL Server licensing remains a separate cost.

Larger Teams (25–50+ users)

At this scale, infrastructure design becomes more nuanced. The considerations shift from individual component specs toward overall architecture.

Physical Server (Recommended)

Virtual Machine – Use with Caution

At 25–50+ users, virtualisation introduces meaningful risk if not engineered carefully. It remains viable andmany large PDM deployments run successfully on well-configured virtual infrastructure, but the margin for error is smaller.

At this scale, separating the SQL server and the PDM archive server onto distinct VMs (or physical machines) is strongly recommended. Combining both roles on a single VM under heavy load creates contention that is difficult to resolve without downtime.

What Does a PDM Professional Server Cost? (25–50+ users)

At this scale, infrastructure costs vary significantly depending on architecture decisions — whether SQL and archive roles are separated, whether the environment is physical or virtual, and whether high availability is required. The figures below reflect a single-server physical deployment as a baseline.

All prices shown exclude VAT.

Physical server (outright purchase — baseline single server)

At this team size, core-based SQL licensing is typically more cost-effective than the Server + CAL model — see the SQL licensing section below for a full comparison.

Cloud VM — Microsoft Azure (monthly recurring)

All-in monthly cost including Premium SSD, Windows Server, and backup: approximately £900–£1,200/month for a deployment of this scale. Architecture complexity at 25–50+ users often warrants a conversation with SolidX before committing to a cloud approach.

Server Software

PDM Professional

PDM Professional requires Microsoft SQL Server Standard (or Enterprise for very large deployments). Unlike PDM Standard, SQL is not bundled — it must be purchased separately through a Microsoft reseller.

Supported SQL versions for PDM Professional 2025 and 2026:

*SQL Server 2017 was dropped at PDM 2024 SP5. If you are running an older SQL version, upgrading before your next PDM version upgrade is essential.

Standard vs Enterprise: SQL Server Standard supports up to 24 processor cores and 128GB of memory per instance. This is sufficient for the vast majority of PDM Professional deployments.

SQL Server Enterprise becomes relevant only for very large vaults, multi-site replication scenarios, or where mission-critical high availability is required. For most engineering teams, Standard is the right choice.

SQL Express should never be used for a PDM Professional production vault. The memory and CPU restrictions make it unsuitable, and it is not a supported configuration.

SQL CAL Licensing

PDM Professional

This is the area that catches the most organisations off guard. SQL is no longer bundled with PDM Professional — it has been sold separately since 2020 and Microsoft’s licensing model for SQL Standard works differently from SOLIDWORKS’ own floating licence model.

We regularly speak to teams who have purchased PDM Professional without realising they also need to budget for SQL Server licensing separately. It is not an obscure requirement, but it is one that gets missed, particularly when the purchase decision is driven by the engineering team rather than IT. Getting it wrong is not just a cost problem, running SQL without the correct licences is a compliance issue.

There are two SQL licensing models to understand:

Server + CAL model

A single SQL Server licence covers the server itself. Each user or device that connects to PDM then requires its own Client Access Licence (CAL).

• CALs are not floating — they do not work like SOLIDWORKS network licences
• You can licence by user or by device, whichever is the smaller number
• A user who connects from multiple devices needs only one User CAL
• Multiple users sharing a single device (e.g. a shared workshop PC) need only one Device CAL for that machine

Example: 2 CAD Editors on dedicated workstations and 5 Viewer licences shared across 10 people = 1 Server licence + 12 User CALs.

This model suits smaller teams with a stable, countable user base and is typically the most cost-effective approach for most PDM Professional customers.

Core-based licensing

Rather than counting users, you licence every physical core on the SQL server (minimum 4 cores, purchased in 2-core packs). There are no CALs required under this model.

This suits larger organisations where the number of users is high, hard to count, or subject to frequent change. It is also the required model if you are running SQL in a virtualised environment where live migration between hosts is enabled, as the server can move between physical hosts, per-core licensing is needed to remain compliant.

SQL Licensing Costs

What to Budget

Prices below are current UK retail (Microsoft Store / reseller list price, June 2026). Volume licensing and reseller agreements typically come in below these figures, so treat them as a ceiling rather than a fixed cost.

Always confirm with your Microsoft reseller or IT Company – these are approximate prices.

Prices last verified in June 2026.

Server + CAL model

The Microsoft Store bundle includes the server licence plus 10 CALs, which covers most small to mid-size PDM Professional deployments in a single purchase. If you need more than 10 users, additional CALs are purchased separately.

Core-based model

Core-based licensing has no CALs — once the server cores are licensed, any number of users can connect. The minimum of 4 cores applies per physical processor or per VM instance regardless of how many cores are actually in use.

Which model costs less?

For a typical small PDM Professional deployment of 5–15 users, the Server + CAL bundle is almost always the more economical route. Core-based licensing starts to make more sense as user counts grow above 20–25, or where virtualisation with live migration is involved.

A rough crossover point: if your user count multiplied by the per-CAL cost (roughly £165–200 per user) exceeds the minimum core licence cost (roughly £6,800–£7,200 for 4 cores), core-based licensing is worth a comparison quote from your Microsoft reseller or IT Company.

Note: SQL Server 2022 licences are still available and supported with current PDM versions and pricing is broadly similar to 2025. SQL Express (used by PDM Standard) remains free with no licensing cost.

Budgeting guidance

SolidX can help you work through the user and device count before you approach a Microsoft reseller, so you go in knowing exactly what you need. In our experience, the teams most likely to overspend are those who’ve grown from 5 to 15 users without revisiting their original SQL spec – what was correctly sized at deployment has quietly become the wrong model for where they are now.

Windows Server CALs:

Every user or device connecting to the Windows Server hosting PDM requires a Windows Server CAL, purchased separately.

SOLIDWORKS Manage

SOLIDWORKS Manage extends PDM Professional with programme and project management, BOM management, and change control workflows. From an infrastructure and licensing perspective, there are a few important distinctions.

Manage is a significant step up from PDM Professional in terms of what it demands from the database. We always recommend that teams considering Manage have a proper infrastructure review before deployment, not because it is difficult to set up, but because the database growth rate is meaningfully higher than PDM alone, and organisations that don’t plan for that tend to find themselves revisiting the server spec within twelve to eighteen months.

Manage always runs alongside PDM Professional — it cannot be deployed independently. The Manage database must be hosted on the same SQL Server instance as the PDM Professional database.

The Manage database tends to grow faster than the PDM database as records, change orders, and project data accumulate. If you are deploying Manage, monitoring SQL Server memory and storage more closely than a PDM-only deployment is advisable from the outset.

SQL requirements for Manage are identical to PDM Professional — SQL Server Standard or Enterprise, with the same supported version matrix. SQL Express is not supported for Manage in any production environment.

CAL requirements for Manage follow the same SQL Server + CAL or core-based model as PDM Professional. Each user or device accessing Manage connects through the same SQL instance, so CAL counts should reflect the combined user base accessing both PDM Professional and Manage. Windows Server CALs apply here as well.

So Physical, Virtual, or Cloud?

Physical Servers

Best suited to active engineering teams with on-site IT infrastructure and a need for predictable, low-latency performance. For the majority of the teams we work with, this remains the right answer.

Virtual Servers

Viable when resource allocation and latency are strictly controlled. The most common failure mode is CPU oversubscription on a shared host, often invisible until the PDM vault is under real load. Note also that live VM migration between hosts requires core-based SQL licensing to remain Microsoft-compliant.

Cloud Platforms

Microsoft Azure

Amazon Web Services (AWS)

One important note on cloud SQL: PDM does not support hosted SQL instances such as AWS RDS or Azure SQL Database. SQL Server must be installed on the VM itself, not consumed as a managed cloud database service.

Choosing Between On-Premise and Cloud

What Happens When a PDM Server Is Under-Specified?

Under-sizing a SOLIDWORKS PDM environment rarely causes immediate failure. What it creates instead is a slow, accumulating degradation — one that is easy to misdiagnose.

The typical progression looks like this:

Stage 1 — Slow SQL response times The first symptoms are usually small: folders take slightly longer to open, search results lag, workflow state changes feel hesitant. Users notice something is off but cannot point to a specific failure.

Stage 2 — Latency that isn’t network-related Even on a fast local network, an underpowered server introduces internal processing delays. SQL queries queue, disk I/O saturates, and metadata requests slow down. The network gets blamed, but the problem is server-side.

Stage 3 — Everyday vault operations slow down Checking files in and out, opening large folders, running searches — individually these are small operations, but under load they become sequential bottlenecks.

Stage 4 — User behaviour changes This is the stage that tends to go unnoticed by IT teams. Users start working around the system: saving locally, skipping workflow states, reducing how often they check files in. Data governance begins to erode before anyone has flagged a performance issue.

Stage 5 — Scaling becomes reactive Small increases in users create disproportionate performance drops. Upgrades happen under pressure rather than by design. What should have been a planned expansion becomes a full re-architecture.

The key insight here is that most PDM performance problems are not caused by a single point of failure. They emerge from a combination of insufficient SQL memory, limited CPU headroom, slow or oversubscribed storage, and increasing metadata load. The system does not break, it just gradually becomes harder to use.

In our experience working with engineering teams across the UK and Ireland, this pattern is most common in organisations that deployed PDM two or three years ago on correctly sized hardware, then added users, workflows, and file volumes without revisiting the underlying infrastructure. By the time performance becomes a conversation, the gap between what the server was designed for and what it is actually doing can be significant.

What Actually Drives PDM Performance?

Across all deployment types, performance is determined by the same core factors:

• SQL Server memory allocation and configuration
• Storage latency and IOPS capability
• Network latency between client and server
• Vault structure and metadata complexity
• Backup and maintenance processes

A common mistake is treating a CPU upgrade as the solution to a slow PDM environment. In most cases it isn’t. Without addressing SQL configuration, storage throughput, and network latency, additional processing power delivers little practical improvement.

When we carry out performance assessments on under-performing PDM environments, the root cause is almost never the CPU. It is usually SQL memory allocation, storage latency, or a combination of both, often on hardware that looked perfectly adequate on paper at the time of purchase.

Talk to SolidX

Infrastructure, SQL licensing, and CAL requirements all interact and the cost of getting them wrong tends to compound over time, either through performance problems or compliance exposure.

If you are planning a new PDM deployment, migrating to a new server, or trying to understand what licences you actually need before making a purchase decision, we are happy to work through it with you.

We support engineering teams across the UK and Ireland with PDM and Manage infrastructure across Physical, Virtual, Azure, and AWS environments, based on real workload requirements rather than generic specifications.