Database Requirements

Software

• Supported Versions
  • 2005, 2008, 2012, 2014, 2016, 2017 & 2019.
  • All variants above and equal to SQL Express.
• Unsupported
  • Compact or localDb variants.

Database Setup

Security

• Authentication
  • SQL User or Integrated Security.
  • User must have full rights to database.

Recovery Model

• Simple or full.

Growth Strategy

• To prevent fragmentation, we recommend that the initial file and log sizes are set to 100MB with a 50% increase.

Collation

• The collation sequence must be set to the correct collation option for your environment prior to setting up the database.

Database Sizing

Data requirements depend on deployment and integration setup options. Expect more rapid data growth for environments where there is a high audit requirement or where there could be a high number of warnings or errors encountered during the integration. This is true with ERP integration, particularly with inventory based transactional integrations (sales orders, purchase orders, shipping, and receiving.

Size

Exact sizing is difficult to predict, however the following table can be used as a guide to a year’s growth in the database:

Usage	Integrations & Frequency
Low	One integration extracting master data from a database source to a file or FTP Location. Two Integrations integrating with an ERP System on a daily basis.	300 ~ 600
Medium	Three to ten integrations extracting master data from a database source to a file or FTP Location on a daily basis. Three to five Integrations integrating with an ERP System. Two integrations integrating with an ERP System on a weekly basis.	600 ~ 1400
Heavy	Three to ten integrations extracting master data from a database source to a file or FTP Location on a daily or more frequent basis. Five or more integrations integrating with an ERP System on a daily or more frequent basis. Two or more integrations integrating with an ERP System on a weekly basis.	1400+