Margin Master

POS import now detects and explains SQL Server resource failures

Shipped in Margin Master 2026.1005.20913 · October 5, 2026

When a POS import fails because SQL Server ran out of memory or disk space, Margin Master now diagnoses the specific cause, reports it as Critical to telemetry, and shows an import-failure dialog explaining what happened, confirming the data is unchanged, and offering Try Again or Contact Support instead of a generic "No Data Imported" error.

What changed

POS imports no longer silently drop data when SQL Server runs out of memory

If your POS import stops because SQL Server runs out of memory or disk space, nothing in your live data changes—your items, prices, and strategies stay exactly as they were after your last successful import.

SQL Server resource failure diagnosis

The failure message now tells you specifically what went wrong—such as "SQL Server is set to use only 512 MB" or "the computer is low on memory"—and what you can do yourself, like closing other programs or freeing disk space.

New POS import failure dialog

When an import stops, the new dialog tells you exactly what happened, confirms your data is safe, and gives you Try Again and Contact Support buttons—no need to re-download your POS file.

Epicor INFILE import now uses a staging table and atomic swap

Critical telemetry severity for import save failures

Contact Support pre-filled for SQL resource failures

If you choose Contact Support, the form is already filled in with all the technical details—just add anything you noticed and send it.

SQL resource failure classifier and tests

Public help page for SQL Server resource failures

See all Margin Master releases