How to run multiple billing counters on SQL Server
Share one database between QuPOS counters on a LAN with Microsoft SQL Server or free SQL Server Express: install, enable TCP/IP, firewall, connect.
About 45 minutes · Applies to: Supermarket, Barcode Billing, Textile
The built-in SQLite database is perfect for one PC. When two or more counters must sell from the same stock, switch to Microsoft SQL Server. SQL Server Express is free and is enough for most shops.
You will need
- One PC or server for the database
- Microsoft SQL Server or SQL Server Express (free)
- All counters on the same LAN
- One QuPOS licence per counter
Steps
Install SQL Server Express
On the PC that will hold the data (it should stay on during business hours), install Microsoft SQL Server Express with mixed-mode (SQL Server and Windows) authentication and set a strong password.
Enable TCP/IP
In SQL Server Configuration Manager, enable the TCP/IP protocol for the instance and restart the SQL Server service. Start the SQL Server Browser service if you use a named instance such as SQLEXPRESS.
Allow it through the firewall
In Windows Defender Firewall on that PC, allow inbound connections for SQL Server (TCP 1433, or the instance's port) and SQL Server Browser (UDP 1434) on the private network.
Give the PC a fixed IP
Reserve a fixed IP address for the database PC in your router so the counters can always find it.
Connect the first counter
In QuPOS, choose Microsoft SQL Server in the setup wizard (or Settings → Database to move an existing shop), and enter the server (for example 192.168.1.10\SQLEXPRESS), user and password. Test the connection and save.
Connect the other counters
Repeat on every counter with the same server details. All counters now share items, stock, bills and reports.
Tips and troubleshooting
- Put the database PC on a UPS; a power cut during a save is the most common cause of trouble.
- Set up automatic daily backup so a copy of the data leaves the server PC.
- Each counter needs its own licence because each is a separate PC.
Seeing an error message? Look it up on the troubleshooting page.