Database server for PostgreSQL, MS SQL and 1C: how to choose and how much it costs
Servix technical team · Updated
In brief. A database server is selected by three figures: the volume of data worked with every day, the number of concurrent sessions and how the DBMS is licensed. The active part of the database should fit in memory, the data should be on SSD or NVMe in RAID 10, the transaction log on a separate RAID 1, and the RAID controller write cache is acceptable only with a battery. MS SQL Server is licensed per physical core, with a minimum of four licenses per processor, so fewer cores with a high frequency are more cost-effective for it; PostgreSQL does not charge for cores. Ready-made configurations in the Servix catalog as of November 2026: for a database up to 50 GB — Dell R350 for 20,886,000 UZS, up to 200 GB — Dell R450 with Xeon Gold 5317 for 53,889,000 UZS, up to 500 GB — Dell R650 with two Gold 5315Y for 71,512,000 UZS.
This article is for an IT manager whose database has outgrown the current server, or who is buying a separate server for a DBMS for an accounting system, CRM or in-house development. Selecting a server for 1C by the number of users is covered in the hub “Server for 1C”; here we focus on the DBMS itself: what it needs from the processor, memory, drives, controller and network, and how the license affects the choice. The rules are taken from Microsoft and PostgreSQL documentation and 1C methodological materials on ITS, prices from the Servix catalog product pages.
Where server selection for a DBMS begins
Before talking about models, you need answers to four questions.
- How much data is in active use. Not the full size of the database, but the part accessed every day: current-year postings, open orders, reference data. If the active part cannot be estimated, calculate by the full size.
- How many sessions run concurrently and what they are doing: short transactions (a document, an order, a payment) or heavy reports across the entire history.
- Which DBMS and edition. PostgreSQL is free. For MS SQL Server, the edition determines the limits on cores and memory, and the number of cores determines the cost of licenses.
- How long downtime can be tolerated. If an hour or two is acceptable, one server and tested backups are enough. If downtime is unacceptable, a second server with a replica is needed.
Processor: frequency, cores and MS SQL licenses
Frequency determines the speed of an individual query, the number of cores how many queries run in parallel. The balance is set by the DBMS license.
How MS SQL Server is licensed
- In the per-core model, all physical cores of the server are licensed, with a minimum of four licenses per physical processor. Licenses are sold in two-core packs.
- If SQL Server runs in a virtual machine, its virtual cores are licensed, with a minimum of four per machine. Licensing by virtual machine requires Software Assurance or a subscription.
- The "server + client access licenses (CAL)" model is available only for the Standard edition.
- Standard limits: SQL Server 2022 uses no more than 24 cores and 128 GB of memory for the buffer pool, SQL Server 2025 — 32 cores and 256 GB. The free Express edition is limited to one processor or four cores, 1,410 MB of buffer pool and a database size of 10 GB in version 2022 and 50 GB in version 2025.
Hence the rule: a server for SQL Server is more cost-effective when built on fewer fast cores. Here is how many licenses the processors from the ready-made builds in the catalog will require:
Processors in the build | Total cores | Base frequency | Per-core licenses (packs of 2) | What to consider |
|---|---|---|---|---|
1 × Xeon E-2314 | 4 | 2.8 GHz | 4 (2) | you cannot buy fewer than four licenses per processor |
1 × Xeon Gold 5317 | 12 | 3.0 GHz | 12 (6) | the second socket is free: a processor can be added later, together with licenses |
2 × Xeon Gold 5315Y | 16 | 3.2 GHz | 16 (8) | fits within the Standard 2022 limit |
2 × Xeon Gold 6326 | 32 | 2.9 GHz | 32 (16) | Standard 2022 uses only 24 cores, but all 32 must be licensed |
License prices are not in the catalog — we send them in the quote together with the server.
Server for PostgreSQL and for 1C
PostgreSQL does not charge per core, so at the same server price you can take more cores for it — for example, Dell R550 8SFF with two Gold 6326 and 128 GB for 97,598,000 UZS. A many-core server for PostgreSQL is justified when there are many concurrent connections and the queries are short.
If the database runs under 1C, ITS has its own recommendations. For MS SQL — the max degree of parallelism = 1 parameter: one query runs on one core, and its speed is determined by frequency, not by the number of cores. For PostgreSQL — disable power saving (otherwise response latency grows unpredictably) and Hyper-Threading; for MS SQL — enable the "High performance" power plan.
Memory: how much you need relative to database size
The rule for any DBMS: the active part of the database should fit in memory. Then reads come from the cache, and the disks are busy mostly with writes. How memory is divided inside the server depends on the DBMS.
- PostgreSQL. The documentation advises giving 25% of a dedicated server's memory to shared_buffers and not expecting a gain from values above 40%: the rest of the memory works as the operating system cache, which PostgreSQL also relies on. The ITS recommendations for 1C follow the same logic: shared_buffers = RAM/4, effective_cache_size = RAM − shared_buffers. Almost all of the server's memory works as the data cache.
- MS SQL Server. Microsoft recommends limiting max server memory to about 75% of the memory not used by other processes. If a 1C server runs on the same machine, ITS advises reducing the threshold by the amount 1C needs. The main restriction is the edition: Standard 2022 gives the buffer pool no more than 128 GB, Standard 2025 — no more than 256 GB. In a server with 512 GB and SQL Server 2022 Standard, the data cache will still take no more than 128 GB; the rest of the memory goes to other services.
Our sizing guideline: the active part of the database plus 25–50% for growth, plus 8–16 GB for the operating system, plus the memory of the application server if it runs on the same machine. This is Servix's working method, not a manufacturers' standard; monitoring cache hits and disk read waits will show the required amount more precisely. Install modules in equal sets across all processor channels.
Disks: latency matters more than terabytes
For a DBMS, what matters is not sequential speed or capacity but the response time for small random operations. Microsoft considers I/O waits that consistently exceed 10–15 ms per request a bottleneck, and notes that the stated transfer time of modern SSDs and NVMe drives is tens of microseconds. The ITS checklist for MS SQL for 1C separates the requirements and makes them stricter: 10–20 ms for disks with data files and 1–5 ms for the transaction log.
A 7200 rpm hard drive spends an average of 4.2 ms just rotating the platter to the right sector — that is half a revolution, without moving the head. Under load, an HDD array exceeds these thresholds, so SSDs or NVMe drives are used for data and logs, and HDDs are left for backups and archives. Drive types and interfaces are covered in the article "Server drives: HDD or SSD, SAS, SATA or NVMe".
A separate volume for the transaction log
The log is written sequentially, while data files are read and written randomly. Microsoft recommends not placing the transaction log on the same physical disk as the data files. The PostgreSQL documentation calls moving WAL to a separate disk an advantage, and ITS advises placing data and logs on different arrays. For tempdb in MS SQL, Microsoft advises a fast volume and, when it competes with production databases, separate disks. ITS for 1C adds partition alignment at 1024 KB and a 64 KB block size for MS SQL files.
A typical layout for a server with eight 2.5″ bays:
Volume | Drives | RAID | Why separate |
|---|---|---|---|
System and software | 2 × SSD | RAID 1 | OS updates and application logs do not interfere with the database |
Data files, tempdb | 4 × SSD | RAID 10 | random reads and writes; half the capacity is usable |
Transaction log (.ldf or pg_wal) | 2 × SSD | RAID 1 | sequential writes with minimal latency |
Why RAID 10 rather than RAID 5 or 6 for a database is explained in the article "RAID 5, 6 or 10: which to choose"; the usable capacity for your set of drives is calculated by the RAID calculator. Use server-grade drives: the PostgreSQL documentation warns that many SSDs hold writes in a volatile cache and by default do not execute the command to flush it. If power is lost, such a drive can lose data that the DBMS already considers written.
Controller cache: only with a battery
A controller with a write cache acknowledges an operation as soon as the data reaches its memory and flushes it to the disks later. In a Microsoft test, 10,000 individual inserts on a 7200 rpm SCSI disk took 84 seconds without a caching controller and 15 seconds with one.
A write cache is acceptable only with power-loss protection. Microsoft states it plainly: any cache must have battery protection, otherwise data corruption and loss are possible, and a UPS does not replace the controller battery. The PostgreSQL documentation advises avoiding controllers with a write cache without a battery; ITS advises checking the battery if the cache works in write-back mode.
- Dell PERC H745 — 4 GB cache, battery, non-volatile cache, RAID 0, 1, 5, 6, 10, 50 and 60. Installed in the R450, R550 and R650 builds from this article.
- Dell PERC H345 — no cache, write-through only, and RAID 0, 1 and 10. For a small database on SSD mirrors this is enough.
Networking
If the application server and the DBMS are on the same machine, the network between them is not involved: for 1C, ITS recommends enabling the Shared Memory protocol in MS SQL in this case. When the roles are split across two servers, every application request goes over the network, and latency matters most: connect the servers directly or through a single 10 GbE switch.
The second stream is replication and backups. A replica on a second server covers hardware failure: MS SQL Standard has basic availability groups for this — two replicas, one database per group; PostgreSQL has streaming replication. With licenses covered by Software Assurance or a subscription, Microsoft allows one passive replica for high availability without separate licenses for it. A separate pair of ports is more convenient for replication and backup. The ready-made builds below have built-in 2 × 1 GbE; we add a 10 or 25 GbE card in the quote.
Configurations by database size and prices as of November 2026
The table is our method, not statistics: memory, cores and disks are calculated using the rules from the sections above. "Sessions" are concurrently working users of an accounting system with short transactions; heavy analytics over the entire history moves the task one row down. Ready-made builds come without drives and with minimum memory: we add drives, modules and a network card to match the calculation.
Active part of the database | Concurrent sessions | Processor | Memory | Disks and controller | Networking | Catalog build and price |
|---|---|---|---|---|---|---|
up to 50 GB | up to 25 | 1 × 4 cores | 32–64 GB | 2 × SSD RAID 1 for data, 2 × SSD RAID 1 for the log; a controller without cache is acceptable | 1 GbE | Dell R350 8SFF, 1 × E-2314, 32 GB — 20,886,000 UZS |
50–200 GB | 25–100 | 1 × 12 cores from 3.0 GHz | 128–256 GB | 4 × SSD RAID 10 + 2 × SSD RAID 1, battery-backed cache | 10 GbE | Dell R450 8SFF, 1 × Gold 5317, 64 GB — 53,889,000 UZS |
200–500 GB | 100–250 | 2 × 8 cores from 3.2 GHz | 256–512 GB | 4–6 × SSD RAID 10 + 2 × SSD RAID 1, battery-backed cache | 10–25 GbE | Dell R650 8SFF, 2 × Gold 5315Y, 64 GB — 71,512,000 UZS |
from 500 GB | from 250 | 2 × 16–32 cores, DDR5 | 512 GB – 1 TB and more | NVMe RAID 10, 8–24 drives | 25 GbE and a second server with a replica | HPE DL380 Gen11 — from 49,000,000 UZS for the platform; Dell R760 — price on request |
Up to 50 GB: one processor and SSD mirrors
The Dell R350 is a single-processor 1U server with eight 2.5″ bays: enough for two mirrors for data and the log plus two more bays for the system. Memory — up to 128 GB in four UDIMM slots. For MS SQL, the four E-2314 cores are exactly the minimum four licenses; if the database fits within the Express limits, you can start with the free edition. If you need a frequency higher than 2.8 GHz, we will build an R350 with a Xeon E-2334 at 3.4 GHz; price in the quote.
50–200 GB: twelve fast cores on one socket
The Dell R450 has one Xeon Gold 5317 — 12 cores, 3.0 GHz, with the second socket free. Not all of the 16 memory slots are occupied, and the platform maximum is 1 TB, so 128–256 GB can be installed without replacing the server. The H745 controller with 4 GB cache and a battery is already included. For MS SQL this means 12 per-core licenses, and a buffer pool of up to 128 GB fits even within Standard 2022.
200–500 GB: two processors and edition limits
The Dell R650 with two Gold 5315Y provides 16 cores at 3.2 GHz — within the Standard 2022 limit, 32 memory slots, up to 2 TB on RDIMM. With 256–512 GB of memory, MS SQL Server 2022 Standard uses only 128 GB for cache, so SQL Server 2025 Standard with its 256 GB limit or Enterprise is chosen. PostgreSQL has no such limits. If eight bays are not enough, see the Dell R750 — up to 24 2.5″ drives, platform configured to specification from 44,000,000 UZS slightly used and 59,000,000 UZS new.
From 500 GB: the current generation and a second server
A large database goes on a DDR5 platform: the HPE DL380 Gen11 and Dell R760 each have 32 memory slots and up to 8 TB, and drive cages for up to 24 NVMe drives. The DL380 Gen11 platform costs 49,000,000 UZS slightly used and 67,000,000 UZS new; processors, memory and drives are selected to specification. For MS SQL to use that much memory for cache, the Enterprise edition is required; plan for a second server with a replica from the start.
Frequently asked questions
How much does a database server cost?
Ready-made builds in the Servix catalog as of November 2026 range from 20,886,000 UZS for a Dell R350 for a database of up to 50 GB to 71,512,000 UZS for a dual-processor Dell R650 for a database of up to 500 GB. Prices are without drives and with base memory; we calculate drives, memory and DBMS licenses in the quote.
When do you need MS SQL Enterprise?
When the Standard limits are not enough: more than 24 cores or 128 GB of buffer pool in version 2022 (32 cores and 256 GB in 2025), availability groups with more than one database and two replicas, online index rebuilds. In other cases Standard is cheaper, and extra cores mean overpaying for licenses.
Can a database be kept on HDDs?
An archive or a rarely updated reporting database — yes. A production database with constant writes — no: under load, HDD latency exceeds the thresholds that Microsoft and ITS specify for data and the log. Keep HDDs for backups.
Physical server or virtual machine?
Both options work. In a virtual machine, MS SQL is licensed with a minimum of four cores per machine, with Software Assurance or a subscription. How to size the host is covered in the hub "Server for virtualization".
How does a server for PostgreSQL differ from a server for SQL Server?
The memory, disk and controller requirements are the same. The difference is in licensing: for PostgreSQL you can take more cores and memory without paying extra for the DBMS, while for MS SQL the number of cores and the edition determine the license cost and the available memory.
Send to [email protected] the DBMS name and version, the database size and annual growth, the number of concurrent users, the application (1C, CRM, in-house development), acceptable downtime and budget. We will select a configuration, calculate drives, memory and licenses, and send a quote. Warranty 12 months, serviced by Servix; made to order, 2–3 weeks, the price is fixed in the invoice; free delivery within Tashkent; prices include 12% VAT.
See also: Server for 1C: configurations for 5–100 users, Server for virtualization: sizing and configurations, RAID 5, 6 or 10: which to choose, Server drives: HDD, SSD, SAS, SATA, NVMe.
Related reading
A server for 1C: how to choose a configuration for the number of users
How to choose a server for 1C for 10, 30, 100 or more users: processor, memory, drives, ready-made HPE and Dell configurations with delivery in Tashkent.
RAID and the server disk subsystem: levels, fault tolerance, controllers
RAID levels for a server: how RAID 4 differs from RAID 5, how many drive failures RAID 6, 10 and 50 survive, why RAID 5 is dangerous on drives of 4 TB and larger. With prices.
Server RAM: RDIMM, channels, ranks, DDR4 and DDR5
How many memory modules to install in a server, why it is important to populate all channels, how RDIMM differs from LRDIMM and MRDIMM, DDR4 or DDR5, how many GB to take for the task.
Lenovo ThinkSystem SR650 V3: overview, configurations and differences from the HPE DL380 Gen11 and Dell R760
Lenovo ThinkSystem SR650 V3: 4th and 5th Gen Xeon, 32 DDR5 slots up to 8 TB, up to 40 drives, XCC2. Comparison with the DL380 Gen11 and R760, price as of November 2026.




