Infor VISUAL SQL Server Memory Sizing Calculator
This calculator sizes RAM for the SQL Server that hosts an Infor VISUAL Manufacturing database and gives a starting value for max server memory. It is built on the share of data VISUAL actually reads every day, not the whole database size.
Your numbers
Data file size used, from sp_spaceused on the VISUAL database.
Share read regularly: recent rows of INVENTORY_TRANS, WORK_ORDER, OPERATION, REQUIREMENT, LABOR_TICKET and the masters.
Planning assumption for connection and session memory.
Report server, backup agent, antivirus.
Your results
Hot share, per-connection memory and headroom are rules of thumb, not Infor figures. Validate with Page Life Expectancy and buffer cache metrics after a month-end close.
Total RAM vs database size
Sweeps VISUAL database size from 10 to 500, holding your other inputs fixed.
Get your VISUAL server memory reviewed
Send your database size, PLE readings and wait stats from a month end and we will check the memory setting and the queries that drive disk reads.
Optional. The tool and every export work without this. No spam.
Why VISUAL is sensitive to database memory
Infor VISUAL is a client-server application: the Windows client on each workstation connects directly to the database, and most of the work is SQL issued by those clients. There is no thick middle tier caching data, so every window that opens a work order, part or customer order reads from SQL Server. When the working set fits in the buffer pool, those reads come from memory; when it does not, they go to disk and users feel it. Busy tables include INVENTORY_TRANS, WORK_ORDER, OPERATION, REQUIREMENT and LABOR_TICKET, but only their recent rows are hot. Connection count also matters because each client keeps its own connections open.
Formula and worked example
Buffer pool target = database GB x hot share x (1 + growth headroom). Connection memory = clients x MB per connection / 1024. Total RAM = buffer + connections + OS reserve + other services. Max server memory = (total - OS - other) x 1024 MB. With the defaults, a 60 GB database with 40% hot data and 25% headroom needs a 30 GB buffer pool. Sixty clients at 5 MB add about 0.3 GB. Adding 4 GB for the OS and 2 GB for other services gives about 36 GB, so install 48 GB. Max server memory from the computed total is about 31,000 MB; if you install 48 GB, set it from the installed figure instead, about 43,000 MB, leaving the OS and services their reserve.
- Set max server memory explicitly; the default lets SQL Server take almost all RAM
- Recalculate the setting from installed RAM, not from the estimate
- Leave room for backup and antivirus processes
Edition limits and licensing notes
SQL Server Standard edition limits the buffer pool memory a single instance can use (128 GB in SQL Server 2016 to 2022; check the edition limits page for your exact version). Most VISUAL databases fit well within that. If your hot data really needs more, compare the cost of Enterprise edition against archiving old history or tuning the heaviest queries first. Standard edition is licensed per core or per server plus CAL, and prices change, so take cost figures from your reseller rather than from any calculator. Running the report server on the same box saves a licence but competes for memory; that is what the other-services input is for.
How to check the result
After a full month including month-end close, read Page Life Expectancy and buffer cache hit ratio from sys.dm_os_performance_counters (Buffer Manager object). A PLE that collapses during MRP or costing runs means the working set does not fit. Check sys.dm_os_wait_stats: high PAGEIOLATCH waits point to reads from disk. Compare the buffer pool size used per database with sys.dm_os_buffer_descriptors to see how much VISUAL actually holds. If memory looks fine but users still wait, the problem is likely blocking or a missing index, not RAM.
Frequently Asked Questions
What is the Infor VISUAL ERP system?
Infor VISUAL, often called VISUAL Manufacturing, is an ERP for make-to-order and engineer-to-order manufacturers, originally developed by Lilly Software. It covers estimating, customer orders, work orders, scheduling, inventory, purchasing, shop floor labor and financials, and runs on SQL Server or Oracle with a Windows client.
How much RAM does an Infor VISUAL database server need?
Enough to hold the data VISUAL reads regularly plus the OS and other services. That is usually a fraction of the database size, because old history is rarely touched. Use this calculator with your own hot-data estimate and verify Page Life Expectancy after a month end.
What should max server memory be for VISUAL?
Installed RAM minus what the OS and other services on the server need, set explicitly with sp_configure. On a dedicated 48 GB server with a 4 GB OS reserve and 2 GB for other services, that is about 43,000 MB. Never leave the default on a server that also runs other software.
Is SQL Server Standard enough for VISUAL?
For most VISUAL installations, yes. Standard edition's memory and core limits are above what typical VISUAL databases need. Consider Enterprise only if the hot data truly exceeds the Standard buffer pool limit for your version or you need Enterprise-only features, and check the limits for your exact SQL Server version.
If you want your team to ask VISUAL questions in plain English on your own servers, we can add a private AI layer that reads a reporting copy so production memory is not touched.
Related Tools
Infor VISUAL Upgrade Cutover Window Calculator
Estimate the downtime and rollout effort of moving Infor VISUAL to a new version: database window, client installs and retesting macros and reports.
ERP Migration & SelectionInfor VISUAL Upgrade Readiness Checklist
A grouped checklist covering backups, customisations, reports, interfaces, testing and cutover for a VISUAL upgrade.
Developer ToolsSQL Server Wait Types Reference for ERP Databases
Searchable lookup of common SQL Server wait types with plain-language meaning, typical cause in an ERP workload and the first thing to check.
ERP OperationsSQL Server Index Maintenance Checklist for ERP Databases
A practical checklist for index rebuilds, reorganizes, statistics updates and verification on SQL Server hosted ERPs.
More Other ERPs tools
See all- Infor VISUAL Private AI Layer Blueprint Generator
- Infor VISUAL AI Assistant Sizing and Value Calculator
- Infor VISUAL INVENTORY_TRANS Type and Class Reference
- Infor VISUAL Sales and Purchasing Columns Reference
- Infor VISUAL Open Customer Order Backlog Query Generator
- Infor VISUAL Work Order Status and Structure Reference
- Infor VISUAL Manufacturing Scheduling Checklist
- Infor XA (MAPICS) Period End Close Checklist
- Infor VISUAL Database Table Reference
Keep exploring
Free tools
- Infor VISUAL AI Assistant Sizing and Value CalculatorSize the GPUs and estimate the monthly value and payback of a private, on-prem AI assistant for Infor VISUAL.
- Infor VISUAL Private AI Layer Blueprint GeneratorFill in your Infor VISUAL environment and get a ready-to-share architecture plan for a private, on-prem AI assistant.
- Infor VISUAL SQL Query Generator for Work OrdersBuild a SQL Server query for open or late VISUAL work orders by filling a few fields, then copy it into your query tool.
ERP fixes and how-tos
- Private AI Layer for Infor VISUAL On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to Infor VISUAL on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
- Infor VISUAL system requirements: server, SQL Server, client and networkWhat to check before installing or upgrading Infor VISUAL: Windows and SQL Server support, client and ODBC needs, network and sizing, and where to get exact specs.
- Infor VISUAL query tool and shop resource maintenanceHow to query Infor VISUAL data safely with SQL or the built-in query options, and how shop resources are defined and maintained for scheduling and costing.
Runs with your ERP
- MachineMetrics Connector for Infor VISUALHow the MachineMetrics VISUAL connector sends work orders to operator tablets and writes labor tickets back over a direct SQL Server link: setup, pitfalls.
- 1 EDI Source EDI Integration with Infor VISUALHow 1 EDI Source connects Infor VISUAL to trading partners for EDI orders, invoices and ship notices via ION or direct API: setup, pitfalls and private AI.
- Infor VISUAL Shop Floor Mobile for Labor TrackingHow Infor VISUAL Shop Floor Mobile captures clock-ins and labor data from shop-floor devices directly into VISUAL: data flow, setup, pitfalls and private AI.
Integrations
- How to build an MCP server for Infor VISUALHow to build a Model Context Protocol server for Infor VISUAL: tool design, SQL Server access, stdio vs HTTP, permission scoping and audit for any MCP client.
- How to add AI agents to Infor VISUALHow to add AI agents to Infor VISUAL: a read-first tool layer over the SQL Server database and API toolkit, with human approval before any write-back.