How to Change SOLIDWORKS PDM Database Recovery Model

SOLIDWORKS PDM uses Microsoft SQL Server to manage its database, which consists of one primary data file (.mdf) and at least one transaction log file (.ldf). The data file stores all physical content in the database, while the transaction log records changes and updates. By default, SQL databases use the Full recovery model, which allows the transaction log to grow indefinitely as regular backups are captured, potentially consuming all available disk space and rendering the database unusable.

We’ve encountered situations where the transaction log file grows uncontrollably, eventually filling the available disk space and impacting SQL Server performance—along with overall vault stability. If you’re performing regular daily backups of the vault database, we recommend switching to the Simple recovery model to prevent the transaction log from becoming excessively large.

If the transaction log file has reached its maximum size or the disk does not have enough free space in the log location, PDM users may see errors such as ‘Error accessing the database’ or ‘Transaction log is full’.

This guide provides step-by-step instructions for checking the size of the transaction log as well as switching the recovery model from Full to Simple to help manage log file growth more effectively.

Full

• • • Transaction log keeps all changes made to the database until a log backup is taken.
    • This allows for point-to-time recovery (e.g. restore the database to exactly 3:12 PM on July 8th).
    • Requires a regular backup schedule for full database backups and transaction log backups to prevent the log from growing indefinitely.
    • The log file can grow significantly if not backed up frequently.

Simple

• • • Transaction log keeps enough information to recover from the last full/differential backup.
    • No point-to-time recovery. You can only restore it to the point of the last full/differential backup.
    • Log is automatically truncated after each checkpoint. The log file size stays manageable.
    • Ideal when daily backups are performed and minor data loss is acceptable since the last full backup.