Tally runs in more small and mid-sized businesses than almost any other accounting package, and hosting it on a Windows VPS is a standard way to let several people post entries from different locations against one company data set. The ODBC layer between Tally and whatever reads its data is where most integrations quietly break.
How Tally Exposes Its Data
Tally is not a conventional database server. The company data lives in Tally’s own format, and access is provided through the Tally ODBC driver, which speaks on a configurable port — 9000 by default. Any external tool that reads Tally data uses that driver; it does not connect to SQL Server or any other RDBMS directly.
That distinction explains most integration failures. Someone expecting a normal database connection configures a SQL Server DSN, which will never work. The correct DSN type is the Tally ODBC driver, and the connection parameters are host and port rather than server, database, and credentials.
Installing the ODBC Driver Correctly
Install the ODBC driver on every machine that needs to read Tally data — including the VPS itself if a reporting tool runs there. There are separate 32-bit and 64-bit drivers and they are not interchangeable; a 32-bit reporting tool needs the 32-bit DSN even on a 64-bit OS.
After installing, open the correct ODBC Data Source Administrator (the 32-bit one at SysWOW64 if needed) and create a System DSN rather than a User DSN. User DSNs are tied to the account that created them, which fails the moment a service or a different user tries to use the connection.
Port Configuration and Firewall Rules
Change Tally’s default ODBC port from 9000 to something less predictable, and set it explicitly in Tally’s configuration rather than relying on the default. Then create an inbound firewall rule for that port scoped to the addresses that need access — the office network and any known integration server.
If the integration runs on the same VPS as Tally, use the loopback address for the connection rather than the public IP. Loopback avoids the firewall path entirely and removes latency, and a same-machine integration should never take the long way around.
Licensing for Multi-User Access
Tally licences are per-company and multi-user licences are tiered — silver for one user plus one concurrent, gold for unlimited within the licensed company. Hosting changes nothing about that: the licence determines how many simultaneous users can open the company, not the server capacity.
Check the licence type before you promise simultaneous access to a team. Running a single-user licence on a VPS and expecting three people to post entries will produce lock conflicts, not a capacity warning. The server will look fine while the users argue about who gets to save first.
Sizing Tally on a VPS
Tally is a 32-bit application in most deployments, which caps its addressable memory regardless of how much RAM the VPS has. Four gigabytes is sufficient for a moderate company with two to four concurrent users; adding more RAM past that point does not speed up Tally itself, though it helps Windows and any co-hosted integration tooling.
What does matter is single-core clock speed and disk latency. Tally’s voucher entry is largely single-threaded, so a fast two-core plan outperforms a slow four-core plan. Verify disk latency before migrating a live company; the data files are small but written on every voucher save. Benchmark during a voucher-heavy operation rather than at idle, because idle latency on an oversold host tells you almost nothing about month-end close. If you see response times above roughly 20 milliseconds at the ninety-fifth percentile while saving vouchers, the storage is the bottleneck and a higher tier with dedicated NVMe is the fix.
Testing the Integration Before Go-Live
Bring Tally up, load the company, and confirm the ODBC DSN connects from the reporting tool. Then run the specific queries the integration will use — not a generic connectivity test. A connection that succeeds but cannot read the voucher table is a common outcome and is invisible to a simple ping-style check.
Test with the company open in multi-user mode and at least one other user logged in, because some tables behave differently under lock. Our Windows VPS plan comparison shows which tiers offer the higher clock speeds that matter for Tally’s single-threaded work.
Backups and Data Safety
Use Tally’s own backup function on a schedule, and additionally take a file-level backup of the data folder. Tally’s backup is consistent by construction; a raw file copy taken while users are posting is not. Schedule the file-level copy for a window when nobody is entering vouchers.
Keep backups off the VPS entirely — a copy on the same disk protects against a mistaken deletion and nothing else. Confirm the restore path works by restoring into a scratch company before you need it.
Common Failure Modes
The three most frequent problems are a 32-bit tool pointed at a 64-bit DSN, a User DSN created under the wrong account, and a firewall change that closed the ODBC port during an unrelated maintenance task. All three produce generic “cannot connect” errors that send people looking at Tally itself.
Keep a note of the DSN name, the port, and the licensed user count next to the server documentation. When the integration breaks six months later, that note is the difference between a five-minute fix and an afternoon of guessing. The comparison table on our homepage lists the plan details relevant to running Tally with a co-hosted integration.



