Margin Master Handbook
- Prerequisites
- Firewall and Network Requirements
- Microsoft Edge Download Block
- SQL Server Authentication Setup for IT Administrators
- Antivirus and Endpoint Security Exclusions
- SQL Server Tools
- Install or Upgrade SQL Server Express
- Install or Upgrade SQL Server Management Studio
- A Tour of the Main Window
- The Menus
- The Button Row
- The Main Data Grid
- The Summary Section
- Banners and Badges
- The Options Window
- Store Configuration
- Miscellaneous
- Export Options
- Vendor Settings
- POS / Connections Tabs
- Background Service
- AI Assistant (Experimental)
- How POS Import Works
- Supported Point-of-Sale Systems
- Data Import Workflows
- RockSolid POS Import
- Epicor Eagle FTP Import
- Epicor MySQL Compass Import
- Transact POS Import
- Paladin POS Import
- Falcon POS Import
- Spruce POS Import
- Bistrack POS Import
- RockSolid Max POS Import
- ECS POS Import
- Prosperity POS Import
- Catalyst POS Import
- Westlake POS Import
- MI9 POS Import
- AS/400 POS Import
- CounterWorks POS Import
- Dimension POS Import
- PacSoft POS Import
- ProStix POS Import
- Sympac POS Import
- Propello POS Import
- EagleVision POS Import
- MySQL/Compass Connection Configuration
- ECI VPN Requirement (Spruce, RockSolid MAX)
- Propello POS Integration Guide
- MI9 Data Pipeline — Import to Main Table
- Troubleshooting: Epicor Import Brought In 0 SKUs
- PACE POS Import
- Advantage POS Import
- General Store POS Import
- J-3 POS Import
- KeyStroke POS Import
- AutBusSystem POS Import
- Tomax POS Import
- Enterprise POS Import
- Computakey POS Import
- Redisell POS Import
- DART POS Import
- MIB POS Import
- Substruct POS Import
- DMAS POS Import
- RODS POS Import
- Procom POS Import
- Agility POS Import
- Acumen POS Import
- Cruise POS Import
- LSandE POS Import
- Retalix POS Import
- DIBCorp POS Import
- GMROI POS Import
- ECi Advantage POS Import
- Sunray POS Import
- ActivantAutomotive POS Import
- IBS POS Import
- Versys POS Import
- RMS POS Import
- TAMS POS Import
- Integrasoft POS Import
- Dynamic POS Import
- Microsoft ARS POS Import
- CDS POS Import
- Spartan POS Import
- Nitterhouse POS Import
- Jeds POS Import
- Theisens POS Import
- Emery Jensen POS Import
- SMS Pro POS Import
- Burdens POS Import
- Intact POS Import
- Bloom Retail POS Import
- NCR Counterpoint POS Import
- Horizon POS Import
- Cloud Vendor Data Sync
- Data Aging and Freshness Warnings
- Resetting Vendor and POS Data
- Rebuild Data and Rebuild Selection Lists
- Troubleshooting Vendor Sync
- Understanding the Strategy Hierarchy
- Pricing Strategies
- Creating a Strategy Step
- Updating and Deleting Steps
- Reviewing a Strategy and Running It
- Shared (Premade) Strategies
- SKU-Level Exceptions
- Manage Custom Groups
- Strategy Execution Cloud Tracking
- Importing from Excel
- Cost Break Analysis
- Cost Break Strategies
- Min/Max Strategies
- Strategy Backup & Restore
- Add Items from Catalog
- Store Grouping
- Data Diagnostics and Missing Index Recommendations
- System Diagnostics
- Margin Master Cannot Save Settings
- SQL Server 2025 Express vs. Full License
- Support Issue Management
- Catalog Lookup
- What's New After an Update
- Version History
- Documentation and the Help Buttons
- CTLD — Do It Best Catalog File
- MARGIN_MASTER — Ace Catalog File
- PCDITEMXREF — Do It Best SKU Classification File
- SAP_ZONE_PRICE_MARGIN_MASTER — Ace Zone Pricing File
- PCDPRODCLASS — Do It Best Product Classification Hierarchy File
- SAP_STORE_DEPT_ZONE_MARGIN_MASTER — Ace Store Zone Assignment File
- Taxonomy — Ace Product Classification File
- Mapp_Pricing — Ace MAP & IMAP Pricing File
- margin_mstr_plano — Ace Planogram File
On This Page
SQL Server 2025 Express vs. Full License
What is this?
Margin Master installs on SQL Server, and most customers run it on SQL Server Express because it's free and it's what ships by default. Express is genuinely fine for a single store with a moderate catalog. It stops being fine once a store's data, store count, or transaction volume grows past what the edition allows. This guide lays out where those limits sit for SQL Server 2025 Express and what a full license (Standard or higher) removes.
Side-by-Side Comparison
| Capability | SQL Server 2025 Express | SQL Server Standard / Enterprise |
|---|---|---|
| Maximum database size | 50 GB per database (increased from 10 GB in SQL Server 2022 and earlier Express versions) | No limit imposed by the edition. Bound only by disk and hardware. |
| CPU utilization | Lesser of 1 socket or 4 cores, regardless of how many cores the server has | Full use of licensed cores. Standard edition supports up to 24 cores per instance. |
| Memory (buffer pool) | Approximately 1.4 GB per instance | Standard edition supports up to 128 GB. Enterprise is effectively unlimited. |
| SQL Server Agent | Not included. No native job scheduler. | Included. Scheduled jobs, alerts, and operators are fully supported. |
| Maintenance Plans | Not available in SSMS | Available. Automated backup, index, and integrity check plans. |
| High availability | None. No Always On, no failover clustering, no log shipping. | Always On Availability Groups, failover clustering, and log shipping supported (edition dependent). |
| Concurrent connections | Not capped by a hard connection limit, but throughput is constrained by the 4-core / 1.4 GB ceiling above | Scales with licensed hardware. Handles many more concurrent Margin Master and POS-integration connections without contention. |
| Licensing cost | Free | Licensed per core or per server/CAL. Cost scales with deployment size. |
Note on the 2025 size increase: Microsoft raised the Express database size cap from 10 GB to 50 GB with SQL Server 2025. That's a real improvement and it buys most single-store customers a lot of headroom. It does not touch the CPU or memory ceiling, which is where most performance complaints actually come from.
SQL Server 2025 Express: What's Actually Limited
Database size
50 GB per database. This is an increase from the 10 GB cap on SQL Server 2022 and earlier. It applies per database, not per instance, and it does not include the transaction log.
Compute
Express can use the lesser of 1 socket or 4 cores, no matter how many cores the server actually has, plus roughly 1.4 GB of buffer pool memory per instance. This is the ceiling that causes slowdowns on busy multi-register or multi-store setups long before the database gets anywhere near the size limit.
No SQL Server Agent
Express does not include the SQL Server Agent service, and SSMS has no Maintenance Plan option against an Express instance. There is no built-in way to schedule backups, index maintenance, or integrity checks. The usual workaround is a scripted job through Windows Task Scheduler, which works but has to be built and maintained outside SQL Server itself.
No high availability
No Always On Availability Groups, no failover clustering, no log shipping. Backup and restore is the only continuity option.
When a Full License Is the Right Call
None of this means every customer needs to upgrade. Most single-store Margin Master installs run comfortably on Express, especially now with the 50 GB ceiling. The signals below are what indicate a store or chain has outgrown it.
| Signal | Why It Happens | What To Do |
|---|---|---|
| Database approaching 50 GB | Item, pricing, and history tables in Margin Master grow with SKU count, store count, and years of retained history. A store with a large catalog or several years of pricing history can approach the Express ceiling. | Upgrade before the database hits the limit. Once the 50 GB ceiling is reached, further growth stops and writes can fail. |
| Multiple stores or a growing chain on one instance | Each additional store adds concurrent connections and transaction volume against the same 4-core / 1.4 GB ceiling. | Multi-store or multi-register deployments on a single instance typically outgrow Express well before hitting the size cap. |
| Need for automated backups or maintenance | Express has no SQL Server Agent and no Maintenance Plans, so backups and index maintenance must be scripted through Windows Task Scheduler instead of managed inside SQL Server. | A full license removes the need for scripted workarounds and gives Margin Master support a supportable, standard maintenance setup. |
| Slow performance during peak hours | Once the buffer pool and CPU ceiling are saturated, query response time degrades even though the database itself is nowhere near 50 GB. | This is a resource ceiling, not a size problem. Upgrading the edition (not just adding RAM) is what raises the ceiling. |
| Disaster recovery requirements | Express supports basic backup and restore only. No Always On, clustering, or log shipping. | Standard or higher is required if the store needs a warm standby or automated failover. |
Quick Reference
- SQL Server 2025 Express: 50 GB database size cap, 4 cores max, about 1.4 GB memory, no SQL Server Agent, no high availability, free.
- Full license (Standard or higher): no database size cap tied to the edition, scales with licensed hardware, includes SQL Server Agent and Maintenance Plans, supports high availability options, licensed cost.
If you are on an older Express version (2022 or earlier), Margin Master's built-in guided installer can upgrade you to a newer SQL Server Express in place — see SQL Server Express Install & Upgrade. For tuning an existing instance, see SQL Optimization.
