How does SOLIDWORKS PDM work across multiple sites?
SOLIDWORKS PDM Professional can place an archive server at each office so users retrieve replicated physical files locally while the vault remains centrally controlled. Database traffic still goes to the central SQL server unless a separate database-replication design is justified. PDM Standard does not provide the multi-site replication capabilities described in the Professional documentation.
Engineering and IT teams comparing one central PDM vault, archive replication, database replication, or a cloud collaboration alternative.
A fixed-price quote or final infrastructure design. Network, SQL, security, backup, user, workflow, and migration requirements must be discovered first.
The two traffic paths in a PDM vault
SOLIDWORKS PDM separates file content from database information. Physical files move through the archive server. File cards, searches, references, status, and other vault information depend on the database. That is why “the remote office is slow” is not specific enough to choose an architecture.
Archive traffic
Parts, assemblies, drawings, and documents are retrieved from the archive server into the local vault view. File size and WAN speed matter.
Database traffic
Browsing, cards, searches, Contains, Where Used, and vault activity rely on SQL data. Latency and query usage matter.
Write authority
Even with database replication, SOLIDWORKS documentation says writes continue to the primary SQL server.
Four architecture patterns
| Pattern | Best fit | Main tradeoff | Key requirement |
|---|---|---|---|
| One central vault | One primary office or acceptable connectivity for all users. | Remote users depend on WAN performance for both file and database traffic. | Measured user experience, resilient connectivity, backup, and recovery. |
| Central database with replicated archive servers | Remote offices mainly struggle when retrieving large physical files. | Database operations still cross the WAN. | PDM Professional, archive servers, replication rules, schedules, storage, and monitoring. |
| Archive plus vault database replication | High-usage sites where SQL read latency is also a demonstrated problem. | More SQL, licensing, availability, administration, and failure-mode complexity. | PDM Professional and a qualified SQL Always On Availability Groups design. SOLIDWORKS describes this for high latency, typically over 50 ms, and high usage. |
| Cloud collaboration or PLM path | Teams whose primary need is browser access, external collaboration, or a different data-governance model. | Different workflow, capability, migration, and administration model from an on-premises PDM vault. | Role, security, file ownership, CAD integration, and process review. |
Archive replication is not database replication
Archive replication creates a local copy of physical vault files at remote archive servers. When a file has already replicated, the user retrieves it from the local server. When it has not, PDM can replicate it when first requested. This directly addresses large-file transfer over a slow WAN.
Vault database replication is a separate PDM Professional capability built around SQL Always On Availability Groups. It can direct eligible read operations to a secondary SQL server while writes continue to the primary. SOLIDWORKS documentation describes it for high-latency, typically more than 50 milliseconds, and high-usage environments. That threshold is a reason to measure, not an automatic design rule.
Diagnose the slow action before adding a server
Time representative tasks at each site: login, folder browse, search, data-card load, Contains, Where Used, Get, check out, check in, and large assembly retrieval. The pattern tells you whether the main constraint is archive transfer, database latency, client configuration, network stability, or a broader workflow issue.
What drives multi-site PDM cost?
A responsible budget separates recurring licenses and infrastructure from implementation and ongoing ownership. The total depends on the design, not only the number of CAD users.
| Cost layer | Discovery questions | Why it changes the budget |
|---|---|---|
| PDM license mix | How many CAD editors, contributors, viewers, administrators, browser users, and integrations need access? | User roles and access patterns determine the required PDM Professional license mix. |
| Server and storage | How many archive locations, how much active and historical data, what growth, and what recovery objectives? | Local archive servers add compute, storage, backup, monitoring, patching, and replacement responsibilities. |
| SQL architecture | Is database replication actually required? What SQL edition, availability, backup, and administration are already in place? | Database replication adds infrastructure and operational complexity beyond archive replication. |
| Network and security | What are the measured latency, bandwidth, firewall, identity, remote-access, and security requirements between sites? | Connectivity and security design can be as important as the PDM configuration. |
| Migration and cleanup | How many files, references, duplicates, revisions, naming conflicts, permissions, and legacy folders must move? | Dirty data and unresolved ownership expand migration, validation, and cutover work. |
| Workflow and integration | How many workflows, approval states, notifications, tasks, ERP exchanges, templates, and automated outputs are required? | Process configuration and integrations add implementation and testing effort. |
| Training and operations | Who administers the vault? How are users trained, supported, audited, and onboarded? | A technically correct vault still fails if ownership and operating procedures are missing. |
The discovery sequence before a quote
Map users, sites, and work
Record location, role, concurrency, CAD tools, typical assemblies, file sizes, shared processes, and external collaborators.
Measure the current network
Capture latency, bandwidth, stability, and timings for representative database and file-transfer actions.
Design the minimum sufficient architecture
Start with the simplest pattern that meets performance, security, availability, and recovery requirements. Add replication only for a measured need.
Pilot and validate
Test representative assemblies, searches, references, permissions, workflows, replication timing, backup, and recovery before the organization-wide cutover.
Frequently asked questions
Can SOLIDWORKS PDM support multiple office locations?
Yes. SOLIDWORKS PDM Professional supports archive replication so each office can retrieve replicated physical files from a nearby archive server while the vault remains centrally controlled. PDM Professional also supports database replication for specific high-latency and high-usage environments.
What is the difference between PDM archive replication and database replication?
Archive replication places copies of physical vault files on archive servers closer to remote users. Database replication uses SQL Always On Availability Groups so eligible read operations can use a secondary SQL server, while all writes still go to the primary database. They address different parts of the user experience.
Does SOLIDWORKS PDM Standard support multi-site replication?
No. The SOLIDWORKS documentation identifies archive and vault database replication as PDM Professional capabilities. A multi-site design that depends on replication should be scoped around PDM Professional, the required server components, and the SQL architecture.
How much does a multi-site SOLIDWORKS PDM deployment cost?
There is no responsible single price without the user, site, server, SQL, migration, workflow, integration, security, and support requirements. The budget combines PDM Professional licenses, server and SQL infrastructure, implementation, data migration, validation, training, backup and recovery, and ongoing administration.
Primary sources
- SOLIDWORKS 2026 Help: PDM server components, archive, database, Web2, Web API, distributed environments, and PDM Professional replication.
- SOLIDWORKS Help: Archive replication overview, physical-file behavior across WAN-connected offices.
- SOLIDWORKS Help: Vault database replication, high-latency guidance, SQL secondary reads, and primary writes.
- SOLIDWORKS 2026 Help: PDM Standard and Professional architecture, database and server-component differences.
Scope the architecture before pricing the vault
Bring the site map, user roles, representative assemblies, network measurements, migration size, workflows, integrations, and recovery requirements.