enova365

enova365 server requirements calculator

The vendor does not publish hardware specifications — it states that the implementing partner defines them. These recommendations come from our own implementations: specs the system actually runs comfortably on.

Users and deployment mode

1100

Database

1300
130
05

Modules and additional workloads

102,000

Document volume

Enter your average monthly volumes — we use them to estimate the database size.

020,000
020,000
020,000
050,000
110

Annual growth

0.3 GB

Estimated database size

~1.5 GB

How is this calculated?

We multiply the monthly volume by 12 and by the approximate size of a single record, then by the number of years of history. On top of that we add ~0.5 GB for the system configuration itself.

  • 15 KBper document— sales invoice with line items, VAT records and ledger posting
  • 12 KBper document— purchase document with line items, VAT and ledger posting
  • 8 KBper document— warehouse document (goods issue/receipt, transfer) with line items
  • 4 KBper entry— a single ledger entry on an account
  • 512 KBper employee per year— HR and payroll data per employee per year (payslips, absences, declarations)

These are rough figures. Actual size depends on the number of line items per document, analytical descriptions, change history, and whether DMS attachments are stored in the database or on disk.

Recommended configuration

Total vCPU

12cores

Total RAM

42GB

Storage (NVMe SSD)

250GB

SQL Server edition

SQL Standard

SQL Server ~8 vCPU / 24 GB RAM (database after 3 years: ~29 GB) • enova365 HTTP server ~4 vCPU / 14 GB RAM

SQL Server licensing

SQL Server edition
SQL Standard
Licensing model
Server + CAL

1 × server license

15 × CAL (per user or device)

At this user count Server + CAL is usually cheaper. It requires countable, named users.

What drives the licence cost?

You license every core of the machine or VM running the SQL instance — not just the cores the database actually uses. Standard edition supports up to 128 GB RAM and 24 cores per instance; beyond that you need Enterprise (per-core only).

If people outside your company use the system (customer portal, web shop, API integrations), Server + CAL usually isn't viable — choose per-core.

Also check the SQL Server runtime licence available through the enova365 vendor — it is sometimes cheaper than buying a Microsoft licence separately.

Things to watch out for

  • With a single server you license all 12 cores of the machine. Moving SQL to its own machine would cut licensed cores to ~8 — a real saving.
  • Backup: dedicated volume of at least 58 GB, daily full backup + transaction log backup every 15–60 min.
Download PDF

These figures are recommendations based on COMPACT's implementation experience and are not the vendor's (Soneta Sp. z o.o.) official requirements. A final specification requires an analysis of your environment.

Talk to us about your environment →