A simple test would be be to check the time stamp on the back-up. Never rely on an automated process, as things can go wrong. Don’t forget to check the back-ups regularly.An example of this would be a ransomware attack, that locks the PDM servers and the back-up systems. If the back-ups are on the same network, they may be compromised along with the PDM servers. If they’re stored onsite, they may be at risk to the same catastrophes, as the PDM servers. Consider where the back-ups are being stored.Some third part software can back-up SQL databases, but it is wise to recommend and test this.SQL Management Studio installs with Microsoft SQL Server 2014 Standard and can be used to schedule back-ups.If you have remote locations, consider SOLIDWORKS PDM Replication. VPN (virtual private networks) can be slow.Ensure that your network can handle the extra traffic that PDM will add. Having capable servers may not be sufficient, if the network bandwidth is limited.Regardless of how the SQL and PDM components are divided among servers, those components should be the only applications running on these servers.For large implementations, having separate servers for SQL components should be considered.Better performance can be obtained by having separate severs, for each component. Will the Database (SQL) and the vaulted files (Archive) be on one or two separate servers.Also, before the installation of SQL or PDM, some important items should be considered. The recommendations made in the preceding link, should be considered as minimal recommendations. SQL Server 2014 should be installed on a compatible server. SQL Server 2014 Standard must be installed before SOLIDWORKS PDM Professional can be installed. In this article we will look at installing Microsoft SQL Server 2014 Standard, which ships with the SOLIDWORKS installation media disks ( not the downloadable installation file set).

Solidworks 2014 download sql server