Infor VISUAL system requirements: server, SQL Server, client and network
infor visual system requirements
Also searched as
- infor visual sql server requirements
- visual manufacturing server requirements
- infor visual client requirements
Short answer
VISUAL runs on Windows with Microsoft SQL Server, using Windows client workstations. The exact supported Windows and SQL Server versions depend on the VISUAL release, so take them from Infor's release documentation, not from memory. This page lists what to verify, how to size, and where upgrades commonly break.
Applies to: Infor VISUAL, various versions. Exact supported versions must be confirmed in the release notes for your target version.
Verify requirements before install or upgrade
- 1Download the system requirements and release notes for your target VISUAL version from Infor support.
- 2Check the supported Windows Server and SQL Server versions and editions against what you run.
- 3Check the end-of-support dates of your Windows and SQL Server versions, since those drive security risk.
- 4Confirm client OS, .NET and ODBC driver requirements for the workstations or the terminal server.
- 5Verify network: latency between clients and the database, and any WAN or VPN users.
- 6Size CPU, memory, storage and backups using the database size and user count.
- 7Test the upgrade on a restored copy before touching production.
- 8Plan the rollback: full backup and a documented restore time.
Server and database
VISUAL's data tier is Microsoft SQL Server. Which versions are supported changes with each VISUAL release, and older VISUAL versions may not support current SQL Server releases. That is the most common surprise when an IT team upgrades SQL Server for security reasons and finds the ERP unsupported on it.
Plan for SQL memory, fast storage for data and log files, and regular maintenance such as index and statistics updates. Many problems blamed on VISUAL are a neglected database.
Client, terminal server and network
VISUAL is a Windows client application, run locally or published through Remote Desktop Services or Citrix. Clients need the correct runtime components and ODBC settings, and a fast, stable link to the database server. Remote sites over slow links are better served by a terminal server near the database than by a direct database connection.
Upgrade and end-of-life planning
Build a matrix of VISUAL version, Windows version, SQL version and any add-ons or integrations. An integration built on the API Toolkit or a Crystal report may need retesting when anything in the matrix changes. Where the ERP is old and the OS beneath it is out of support, isolating the server on the network and limiting access reduces risk until you can upgrade.
-- Record the current SQL Server version SELECT @@VERSION; SELECT name, compatibility_level FROM sys.databases;
Try it here, free
Infor VISUAL SQL Query Generator for Work Orders
Build a SQL Server query for open or late VISUAL work orders by filling a few fields, then copy it into your query tool.
Common pitfalls
- !Upgrading SQL Server or Windows before checking VISUAL support.
- !Ignoring integrations and reports when upgrading.
- !Skipping a restore test of the backup.
- !Putting remote users on direct database connections over slow links.
- !Leaving the server on an unsupported OS without compensating controls.
How an ERP-grounded AI assistant handles this
If you plan to add an AI layer, it needs only a read-only database connection and some spare hardware, and it runs beside VISUAL rather than inside it. Netray deploys open-weight models on your own GPU servers, so the VISUAL requirements above do not change.
Frequently asked questions
Where do I find the exact supported versions?
In the release notes and system requirements for your VISUAL version, available through Infor support or your reseller.
Can VISUAL run on the latest SQL Server?
Only if your VISUAL version supports it. Check before upgrading SQL Server, because compatibility varies by release.
Does VISUAL need a dedicated server?
Small sites sometimes share, but a dedicated database server with sufficient memory and fast disks is the safer design.
Related
Infor VISUAL error 19005: causes and step-by-step fix
Error 19005 is not a code we can tie to a single documented meaning, and published answers vary. In practice, numbered errors in VISUAL usually come from the database layer: a lost or failing SQL Server connection, an ODBC or client mismatch, or a permissions problem. The reliable way to fix it is to capture the full message text, test the connection outside VISUAL, and check the SQL Server error log.
How-toInfor VISUAL REST API: what exists, the API Toolkit and how to wrap it
Classic Infor VISUAL integrates through the VISUAL API Toolkit (COM objects that apply business logic), direct SQL access for reads, and flat-file or EDI imports. A native REST API is not the traditional route. Most teams expose REST themselves by wrapping the Toolkit or SQL reads in a small service, or use Infor ION where their version and licence support it.
How-toInfor VISUAL query tool and shop resource maintenance
To query VISUAL data, use a read-only SQL login in SQL Server Management Studio or a reporting tool against the VISUAL database, or the in-application query and reporting options your build provides. Shop resources, the machines and work centers that operations are scheduled on, are maintained in the Shop Resource area and drive scheduling, load and costing.
How-toInfor VISUAL report builder: build a custom work order report
VISUAL reports are commonly built in Crystal Reports connected to the VISUAL SQL Server database, and then added to the application so users can run them. A work order report joins WORK_ORDER, OPERATION and optionally REQUIREMENT and PART, filters by work order, and formats it for the shop floor.
How-toInfor VISUAL Price Book: How Customer Pricing and Price Breaks Are Set Up
In Infor VISUAL, a selling price reaches an order line from a hierarchy of sources: the part's list price and quantity breaks, any customer-specific pricing, and manual override on the line. A price book approach means maintaining those sources deliberately and in one place, then testing the result on order entry. Exact window names depend on your version.
AdvancedPrivate AI Layer for Infor VISUAL On-Prem: Reference Architecture
Infor VISUAL runs on SQL Server (or Oracle), so the quickest private AI path is a read-only reporting copy plus a local document index, a tool server with named read actions, and an open-weight model on your own GPUs. Use the VISUAL API Toolkit for writes only, with human approval, and mirror VISUAL user security in the tool server.
AI for ERPAI for Infor VISUAL ERP: Answers and Agents for Job Shops
Add AI to Infor VISUAL ERP for make-to-order and job shop manufacturers: quoting, scheduling, and shop floor answers grounded in live VISUAL data, on-prem.
Stuck on Infor VISUAL (VISUAL Manufacturing)?
Talk to engineers who work inside Infor VISUAL (VISUAL Manufacturing) every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- 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.
- Infor VISUAL and XA Legacy System Risk AssessmentTen questions that score how exposed your VISUAL or XA system is on support, skills, hardware, customisation and integrations.
- Infor VISUAL Upgrade Readiness ChecklistA grouped checklist covering backups, customisations, reports, interfaces, testing and cutover for a VISUAL upgrade.
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 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.
- Infor VISUAL REST API: what exists, the API Toolkit and how to wrap itWhat integration options Infor VISUAL really offers: the VISUAL API Toolkit, SQL access, ION and building your own REST wrapper, plus where to find documentation.
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.
Guides
- Visual Manufacturing to CloudSuite Industrial MigrationMigrate from Infor Visual Manufacturing to CloudSuite Industrial. Understand architectural differences, data migration steps, and timeline expectations.
- AI Visual Inspection for Manufacturing Quality ControlDeploy AI-powered visual inspection systems in manufacturing. Covers defect detection models, camera setup, ERP quality integration, and ROI benchmarks.
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.