Microsoft SQL Server 2025 Standard is Microsoft's mid-tier edition of its relational database engine, released to general availability on 18 November 2025 as version 17.x. This listing covers Standard edition Client Access Licences (CALs) in packs of 2 to 100, delivered digitally by email. Choose the CAL count that matches the users or devices connecting to your server.

What you get in this listing

What is the difference between a User CAL and a Device CAL?

A User CAL licenses one named person to access the server from any number of devices. A Device CAL licenses one device that any number of people may use. The cheaper option depends on your ratio: more devices than people means User CALs; more people than devices — shift work, shared terminals, a warehouse floor — means Device CALs.

The reasoning matters because the choice is made per deployment, not per user. A ten-person office where everyone has a laptop and a phone that both query the database needs ten User CALs rather than twenty Device CALs.

A common issue we see is buyers counting only staff who open a reporting dashboard, and forgetting that application servers and integrations connecting on a user's behalf are also counted under the Server + CAL model.

How many CALs do I need?

Count every distinct user or device that accesses the SQL Server instance, directly or through an application. Under the Server + CAL model you need the server licence plus one CAL for each of those users or devices. Multiplexing — pooling connections through middleware — does not reduce the CAL count.

If your database is reachable by anonymous external users — a public website, for example — Server + CAL is usually the wrong model and per-core licensing applies instead. Message us before ordering if that describes your setup.

What's new in SQL Server 2025 Standard?

SQL Server 2025 is the first release to build AI features into the engine itself. Standard edition also gained headroom: resource limits rose to 32 cores and 256 GB of memory, up from the previous generation's ceiling, which removes a common reason for upgrading to Enterprise.

• Built-in AI and vector search – a native vector data type and vector distance functions for embeddings and RAG-style workloads, reducing the need for a separate vector database. Approximate vector indexes shipped in preview behind an opt-in database-scoped configuration.
• Native JSON – a JSON data type with a supporting JSON index, instead of storing documents as text.
• Regular expressions in T-SQL – RegEx and fuzzy string matching for validation and data cleaning without external code.
• REST API support – call external endpoints from inside the engine through a system stored procedure.
• Change event streaming – push committed transaction log changes to event platforms for real-time, event-driven applications.
• Fabric mirroring – replicate to Microsoft Fabric OneLake for near-real-time analytics without building an ETL pipeline.
• Optimized locking and tempdb resource governance – fewer lock-escalation problems and more predictable tempdb growth, with no application code changes required.

The nuance most upgrade guides skip: several 2025 features are generally available in the engine but still gated behind the PREVIEW_FEATURES database-scoped configuration. Microsoft does not recommend enabling those in production, so plan a proof of concept before depending on them.

Standard vs Enterprise: which edition do I need?

Choose Standard if your workload fits inside 32 cores and 256 GB of memory and you do not need unlimited-scale high availability. Choose Enterprise when you need capacity beyond those limits, multiple readable secondary replicas, or the full advanced availability feature set. Most small and mid-sized deployments fit comfortably in Standard.

System requirements

• Windows Server 2019 or later (Windows Server 2016 and earlier are not supported), supported Linux distributions, or containers
• 64-bit x64 processor; ARM64 is supported by SSMS 22 tooling
• Minimum 4 GB RAM — allocate considerably more for production workloads
• At least 6 GB of free disk space for the engine, plus space for your databases, tempdb and backups
• SQL Server Management Studio 22 for full 2025 support

Upgrading in place is supported from SQL Server 2016 SP2 and later. In practice the host operating system is often the blocker, so a side-by-side migration with backup and restore onto a newer Windows Server build is the usual route.

How to install and activate SQL Server 2025 Standard

1. Download the SQL Server 2025 installation media from Microsoft's official download page.
2. Run the setup wizard and choose a new stand-alone installation.
3. When prompted for an edition, enter the product key supplied in your order email.
4. Select your features — Database Engine Services at minimum — and set the instance name and collation.
5. Configure authentication mode and add your administrator accounts.
6. Complete setup, then install SQL Server Management Studio 22 to connect and verify the version.
7. Record your CAL entitlement with your licence documentation; CALs are counted for compliance rather than entered as a key.

Why buy from Softkeyworld?

• Digital delivery by email — no shipping, no waiting for physical media
• CAL packs from 2 to 100 so you buy only what you need
• Installation and activation support from our team at support@softkeyworld.com
• 7-day return policy on digital goods, in line with our published terms
• UK-registered company: Softkeyworld Ltd, 27 Old Gloucester Street, London WC1N 3AX

Choose your CAL pack and order now

Frequently asked questions

Is SQL Server 2025 Standard available now?

Yes. SQL Server 2025 reached general availability on 18 November 2025, and the GA build is the first one licensed for production use. The earlier 2025 builds released during the public preview were intended for evaluation and testing only.

Does this listing include the server licence or only CALs?

This listing is for Standard edition Client Access Licences in the pack size you select. Under the Server + CAL model a server licence is also required for the machine running the instance. If you need both, contact us before ordering and we will confirm the correct combination for your deployment.

Can I use SQL Server 2025 CALs with an older SQL Server version?

Generally yes — CALs are typically usable with the matching or earlier server versions, since a newer CAL covers access to older releases. Downgrade and version-matching rights vary by agreement type and region, so check your own licence terms or ask us before mixing versions.

How is the licence delivered?

Electronically. After payment clears, your licence details and installation guidance are emailed to the address on your order — usually within a short window during business hours. Nothing is shipped physically.

Will my licence keep working after a hardware change?

SQL Server licences are not tied to hardware in the way consumer Windows digital entitlements are, so replacing hardware does not normally invalidate the licence. Reassignment rules between servers do apply under Microsoft's licensing terms, so review those before moving a licence to a different machine.

What if activation fails during setup?

Most setup-time key errors turn out to be an edition mismatch — a Standard key entered into Enterprise or Developer media — rather than a faulty key. Confirm you downloaded the correct edition, then email support@softkeyworld.com with a screenshot of the error and we will help you resolve it.

Related products

• SQL Server 2022 Standard Edition – Device CAL
• Microsoft SQL Server 2019 Standard
• Windows Server 2025 Standard CD Key
• Windows Server 2025 Datacenter