Prodoc uses Microsoft SQL Server for its databasing and does not support other database engines.
Requirements
There is only one requirement for SQL Server and that's one of versioning, Prodoc only supports versions of SQL Server that are currently in mainstream support by Microsoft, this means that as a version of SQL goes End-of-Life, we may use SQL functions that are not supported by that version.
Notes
- Often newer versions of SQL will introduce functions that can achieve goals that are significantly faster to execute than previous methods, if the query is not hardcoded into the software itself we may be able to workaround these at your time (slower execution) and cost (development time) however this may not always be possible, these workarounds are never recommended and we recommend ensuring you're always on a current mainstream support version for both functionality and security reasons.
- There are no specific SQL Server hardware requirements for Prodoc and recommend following general best practice for SQL server. Prodoc databases start under 1GB and the largest is over 500GB, so please spec according to your needs. Larger databases stem from using Prodoc as a filing cabinet and storing non-Prodoc shipment files (such as a PDF Bill of Lading) against the shipments, which Prodoc then translates to binary and stores them as a blob in the database. If not being used for this purpose, it's common that a database will never exceed 10GB even after many years of use.
- New releases of SQL Server are expected to work out of the box, however if in doubt when upgrading to a very recent release, please contact our support and we may be able to assist in the unlikely event that a rollback is required. Frequent backups are always recommended.
- If running an out of support version of SQL Server, a new Prodoc version could introduce a code-level change that breaks compatibility, this can result in an extended outage for your users until a backup can be restored.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article