Installing SolidWorks PDM actually works if you stop treating it like consumer software
SolidWorks PDM is version control for CAD files. It lives on a Windows server, uses SQL Server behind the scenes, and connects to client machines through a lightweight vault client. That's the summary. The reality involves more moving pieces than most people expect on day one. I followed the official guide the first time I installed this, and it's not bad. It just assumes you already know what you're looking for. The installer doesn't warn you about prerequisites until you hit a wall. Here's what matters, in the order I've learned to do it. First, pick your server. This needs to be a dedicated Windows Server machine, not a domain controller, and definitely not a workstation you use for anything else. SQL Server 2019 or 2022 is required. Express edition works fine for up to about 25 concurrent users. Beyond that, you're looking at Standard or Enterprise, and the licensing cost jumps noticeably. I had a client who tried running PDM on SQL Express with 40 checked-out files in a week. The database hit 10GB, then 12GB, then the backups started failing because Express caps at 10GB per database. Took three days to sort out.
Before you even run the installer, make sure you have: A Windows Server 2019 or 2022 instance with a static IP. DHCP will work but you'll regret it when a vault stops resolving. SQL Server installed and configured. Make sure TCP/IP is enabled in the SQL Server Configuration Manager. Named pipes can stay disabled. The default instance name is fine unless you have a reason to change it.
Administrative credentials on both the server and the SQL instance. The PDM installer needs to create a service account and a database user, and it won't ask twice. Then you run the setup. The PDM Professional installer bundles the server components and the client components together, which is convenient but means you need to make deliberate choices during setup. When it asks what role to install, pick the server role if this is your database host. The client role installs the vault explorer and the SolidWorks add-in. Don't install both on the same machine unless you're testing. It works, but the updates get confusing later. During the database setup, the installer creates the vault database automatically. You give it a name. I always name the vault after the company, not the project. Something like AcmeVault instead of Acme_PDM_2024. You'll thank yourself in three years when you're doing restores and the naming is consistent across everything.
Get the Full Details
After the database is created, you configure the vault settings. This is where people rush. The vault path is where your files live on disk. Default it to a large, fast drive, not the C drive. If you're on a network-attached storage solution, make sure it's a proper NAS with SMB support, not a cheap Synology unit running SMBv1. PDM chokes on SMBv1 and the performance is awful regardless. Create your admin user. The default admin account is fine for day-to-day management. Don't give everyone admin. I watch license counts drop when someone leaves the company and forgets to deprovision the admin access. The client install is straightforward. Run the same installer on each user machine and select the client role. Point it at your server by hostname or IP. The SolidWorks add-in should register automatically if SolidWorks is already installed. If it doesn't show up in the toolbar, you're missing the add-in registration. Run the installer again and verify the SolidWorks integration checkbox is ticked.
Here's something the guide doesn't emphasize enough: testing your checkout workflow before you hand it to anyone. Open SolidWorks, check out a single part, modify a dimension, check it back in. Watch the version number increment. This takes about five minutes and will save you two hours of confused support tickets later. One thing nobody mentions about PDM is how much the search index matters. After installation, the vault search won't return results immediately. The indexer runs on a schedule, usually every 15 minutes by default. If you need instant search results, you can lower the index interval, but that hits CPU and disk performance. I set mine to 5 minutes for smaller teams and leave it alone. The indexer catches up eventually. Another counter-intuitive detail: PDM doesn't lock files the way most people think. A checked-out file is read-locked for everyone else, but the original stays in the vault. The working copy lives in the local cache. When someone checks out a file, they get a cached copy on their machine. This means they can work offline and sync later. It's powerful but it also means file conflicts are rare while stale caches are common. I've seen two engineers modify the same assembly from different cached copies and check in without realizing it. The second check-in overwrites the first. No warning. The PDM conflict resolution is basic compared to actual version control systems like Git. You lose work if you don't communicate.
For backups, PDM stores everything in the vault database plus the physical file store. The database holds metadata, version history, and permissions. The file store holds the actual CAD data. Back up both on separate schedules. I run database backups every four hours during business hours and full vault store backups nightly. Incremental vault backups daily. This gives you a recovery point of roughly four hours for metadata and one day for files. Acceptable for most small to mid-sized operations. There's a real limitation worth stating plainly: PDM doesn't integrate well with non-SolidWorks CAD tools. If your team uses Inventor, Creo, or STEP files from external vendors, PDM will store them but the check-in experience is clunky. The file type recognition is solid for native SolidWorks formats. Everything else is treated as a generic document. You lose features like drawing revision tracking and bill of materials generation for those files. If your shop is mixed-CAD, consider whether PDM is the right tool or whether you'd be better served by a dedicated PLM system like Teamcenter or Windchill, even though those cost significantly more. Update discipline matters too. SolidWorks releases PDM updates quarterly, usually bundled with Service Pack releases. Always update the server before the clients. Installing a newer client against an older server will fail. I've seen this happen during summer downtime windows when IT updates machines at different times. The fix is simple but annoying: restart the SolidWorks PDM Service on the server, then reinstall the client component on the affected machines.
If you're starting from scratch and need the installer, you get it through the SolidWorks portal once you have a valid license. The download page is buried under the Support section. Look for "SolidWorks PDM Professional" under your product downloads. The installer is usually around 2.5GB. Factor that into your bandwidth planning if you're deploying to multiple machines simultaneously. The biggest mistake I see is skipping the permission structure design. Don't wing it. Define your folders, your workflow states, and your user roles before you hand out licenses. A poorly structured vault causes users to check files into the wrong location, break workflows, or accidentally publish restricted documents. Building the structure takes about an hour. Fixing it after six months of messy usage takes about six hours.
