SQL Server for startups

Choose the licensing model before counting application servers

For SQL Server 2022 Standard, compare Server + CAL licensing with per-core licensing before purchasing. Under Server + CAL, each user or device accessing SQL Server needs an appropriate CAL, including indirect access through your application. Connection pooling, shared logins and middleware do not reduce that population. Licensing one application-server service account does not cover its downstream users. For a customer-facing SaaS product with a changing or uncountable audience, per-core licensing is usually the more practical starting point.

Per-core licensing removes the requirement for SQL Server CALs, but it does not automatically settle every SaaS licensing question. Rights to provide hosted software services depend on your agreement and deployment model. Microsoft has separate service-provider licensing arrangements and conditional self-hosting rights; an activation key alone does not establish those permissions. Describe who owns the application, who accesses it and where it runs, then check the applicable Microsoft Product Terms or service-provider agreement before committing to a licence.

• Count indirect users and devices, not just database logins or concurrent sessions.
• Choose User CALs or Device CALs according to who or what accesses the server.
• CAL versions must cover the SQL Server version being accessed; older CALs do not cover newer servers.
• Document SaaS hosting rights separately from the core or CAL calculation.
• Check Windows Server licensing separately if SQL Server runs on Windows.

Size Standard against its actual limits, not the machine specification

SQL Server 2022 Standard's Database Engine compute limit is the lesser of four sockets or 24 cores per instance. Its 128 GB limit refers to buffer pool memory per instance, not an absolute cap on installed RAM or all memory consumed by SQL Server. These distinctions matter when choosing a host: a larger machine may support other workloads, but one Standard instance cannot necessarily use all its processors or turn every extra gigabyte into database cache.

Before moving editions, capture representative workload measurements: CPU utilisation, storage latency, memory pressure, blocking and the most expensive queries. Use Query Store to identify regressions and compare execution plans after changes. Enterprise is not a substitute for fixing missing indexes, oversized result sets or slow storage. Also check the exact feature matrix rather than assuming every advanced capability requires Enterprise: Transparent Data Encryption is available in SQL Server 2022 Standard, although online index operations remain an important edition distinction.

• Measure peak customer activity and batch jobs, not just daily averages.
• Leave memory for the operating system and other processes when configuring SQL Server.
• Test index changes against both read performance and write overhead.
• If using TDE, back up the protecting certificate and private key securely.
• Check edition-specific memory limits separately for specialised features such as In-Memory OLTP.

Design recovery around database boundaries and tested restores

A basic availability group in SQL Server 2022 Standard supports two replicas and one database. Its secondary cannot serve read-only workloads or perform backups, so it is not a way to add reporting capacity. For a SaaS application spread across several databases, separate basic groups also do not provide one coordinated failover unit. Map transactions, shared dependencies and tenant placement before selecting the topology, especially if the application expects multiple databases to remain consistent during a switch.

Availability does not replace backups: accidental deletes and damaging application changes can propagate to another replica. Define recovery point and recovery time objectives, choose an appropriate recovery model, and schedule full, differential and transaction log backups as needed. Then restore them into an isolated environment and measure the result. Include encryption keys, server-level logins, SQL Agent jobs and application connection settings in the runbook; restoring a database alone may not restore a working service after an outage.

• Test failover with application traffic, connection retries and in-flight transactions.
• Keep backup copies protected from the credentials used by the production application.
• For point-in-time recovery, establish and maintain a valid transaction log backup chain.
• Measure restore time using realistic database sizes and available storage bandwidth.
• Verify passive failover licensing rights before leaving a second SQL Server instance deployed.

Audit VM, test-environment and purchase rights before deployment

For SQL Server 2022, licensing an individual virtual machine by virtual cores requires subscription licences or licences with active Software Assurance. Under that option, license the virtual cores allocated to the VM, subject to a minimum of four core licences per VM. Do not apply that calculation automatically to a perpetual licence without Software Assurance. Server + CAL is a separate option for Standard, while physical-core licensing has different counting rules and does not give Standard unlimited virtualisation rights.

Keep a deployment register showing the version, edition, licensing model, assigned server or VM, and evidence of entitlement. Developer Edition can support development, testing and demonstrations, but not live customer service or operational production reporting. A staging label does not change the actual use. Before buying, verify whether the offered item supplies the server entitlement, core quantity or CAL you need, and whether its licensing channel supports your deployment. Successful activation is not proof that those requirements are satisfied.

• Check the current Microsoft SQL Server Licensing Guide and applicable Product Terms together.
• Record Software Assurance or subscription expiry dates where deployment rights depend on them.
• Review licence reassignment and mobility rules before enabling automatic host migration.
• Separate development and test workloads from services that support live business operations.
• Confirm licence transfer documentation where a licence is being resold.

SQL Server 2022 Standard: licensing and deployment checks