SQL Server IoT 2025 is Here: What It Is and Why It Matters for Embedded and OEM Systems

Ken Marlin
Ken Marlin
Supplier Manager
Microsoft SQL Server 2025 Blog

The new SQL Server IoT 2025 is now available! If you build devices, appliances, or embedded systems that ship with a database inside, SQL Server IoT 2025 is worth a serious look. It brings the SQL Server 2025 engine into long-life, fixed-function products. You get the full engine, the same AI features, the same JSON and vector capabilities, and the same security improvements. The only difference is that it is packaged and licensed for OEM and embedded scenarios.

In my experience supporting embedded customers, the pattern is consistent. More data at the edge, tight security requirements, long product lifecycles, and pressure to support AI without adding cloud dependencies. SQL Server IoT 2025 helps you handle those problems without changing how you design your systems. You can use the same T-SQL, drivers, tools, containers, and development workflow.

AI where your device runs

The biggest change in SQL Server IoT 2025 is the built-in AI stack. The database now supports a native vector type, semantic search, hybrid search, and local or remote model execution. You can generate embeddings inside the engine, and you can run AI agents through a secure REST endpoint that SQL Server manages.

Nothing in this requires a cloud connection unless you choose to use one. You can keep models local by using Ollama or ONNX Runtime. You can also call cloud models through Azure OpenAI or OpenAI.

For embedded systems, this means you can build features that previously required a cloud round-trip. Examples include local anomaly detection, troubleshooting assistance, natural language search of manuals or logs, and smarter automation. If you already store your device data in SQL Server, the new vector features let you use that data immediately.

Security that matches modern requirements

The platform is secure out of the box. SQL Server IoT 2025 carries forward the security updates from SQL Server 2025. That includes TLS 1.3, TDS 8.0, PBKDF hashing, managed identities, and stricter defaults. This helps you ship hardware that is ready for audit and compliance checks. For teams in healthcare, manufacturing, or other controlled industries, this reduces significant design risk.

Performance improvements that help small systems

Most devices in the field run on constrained compute, so predictable behavior underload becomes more important than raw horsepower. SQL Server IoT 2025 benefits from improvements like optimized locking, Lock After Qualification, tempdb governance, faster failover, and reduced contention during heavy workloads.

Your device can run more predictable workloads with fewer stalls. It starts faster, handles concurrency better, and gives you cleaner behavior when something on the system misbehaves.

Better ways to move data out of the device

You also get Change Event Streaming, which pushes changes directly to Azure Event Hubs. The engine streams committed transactions without extra system tables. This helps when your design needs low-latency reporting or coordination with services outside the device.

If you use Microsoft Fabric, SQL Server IoT 2025 supports database mirroring directly into OneLake. That gives you a simple path to analytics or long-term storage without writing ETL code.

Developer workflow stays simple

Stability in the toolchain is just as important as stability in the engine. SQL Server IoT 2025 uses the same drivers, SSMS, VS Code extension, containers, and deployment workflow. You also get the new JSON type, JSON indexing, RegEx functions, Base64 utilities, and improved T-SQL functions that SQL Server 2025 introduces.

When an upgrade is worth it

If you are trying to decide whether this upgrade is worth it, these are the points that usually guide the decision:

  • If your device is running SQL Server 2014 or 2016, you are past or near the end of mainstream support and the extended support runway is shrinking fast. SQL Server IoT 2025 offers a long-life option with a modern engine, stronger security, and a cleaner feature set for long-term maintenance. You also get improvements like accelerated recovery, better indexing behavior, and up-to-date drivers.
  • If your product roadmap includes AI features or if customers are asking for analytics without sending data off the device, SQL Server IoT 2025 gives you a built-in way to handle that.
  • If your company is standardizing on Fabric or Azure Arc, IoT 2025 fits neatly into that architecture.
  • • If your design team is trying to reduce custom code around queues, logs, or sync processes, IoT 2025 reduces that work.

SQL Server IoT 2025 Options

EOL

EOS

Part #

SQL SERVER IoT 2025

COA Type

2035

2035

EP2-59891-1P

SQL Svr Std RUNTIME 2025 IoT ESD OEI 1 Clt Std

J-SERIES/
K-SERIES

2035

2035

EP2-59892-1P

SQL Svr Std RUNTIME 2025 IoT ESD OEI 5 Clt Std

J-SERIES/
K-SERIES

2035

2035

EP2-59885-1P

SQL CAL Runtime 2025 IoT ESD OEI 1 Clt Device CAL

J-SERIES/
K-SERIES

2035

2035

EP2-59886-1P

SQL CAL Runtime 2025 IoT ESD OEI 1 Clt User CAL

J-SERIES/
K-SERIES

2035

2035

EP2-59887-1P

SQL CAL Runtime 2025 IoT ESD OEI 5 Clt Device CAL

J-SERIES/
K-SERIES

2035

2035

EP2-59888-1P

SQL CAL Runtime 2025 IoT ESD OEI 5 Clt User CAL

J-SERIES/
K-SERIES

2035

2035

EP2-59894-1P

SQL Svr Std RUNTIME 2025 IoT ESD OEI 4 Core License

J-SERIES/
K-SERIES

2035

2035

EP2-59893-1P

SQL Svr Std RUNTIME 2025 IoT ESD OEI 2 Core Addtnl License

J-SERIES/
K-SERIES

2035

2035

EP2-59890-1P

SQL Svr Ent RUNTIME 2025 IoT ESD OEI 4 Core License

J-SERIES/
K-SERIES

2035

2035

EP2-59889-1P

SQL Svr Ent RUNTIME 2025 IoT ESD OEI 2 Core Addtnl License

J-SERIES/
K-SERIES

 

FAQs

Is SQL Server IoT 2025 different from SQL Server 2025?
The engine is the same. SQL Server IoT 2025 is licensed for embedded and OEM scenarios and includes the support lifecycle those products need. All features come from SQL Server 2025, including AI, vector search, JSON, CES, and Fabric mirroring.

Are there pricing or licensing changes?
No. SQL Server IoT 2025 keeps the same pricing and licensing structure.

Does SQL Server IoT 2025 support both Windows and Linux?
Yes. You can run the IoT edition on either platform, with full feature parity. The Linux engine carries the same improvements as SQL Server 2025, including TLS 1.3, custom password policies, and tmpfs for container workloads.

Can I use SQL Server IoT 2025 offline?
Yes. The product does not require a cloud connection. You can run local models, local inference, local vector search, and local analytics entirely inside the device.

What are the OS and upgrade requirements?
Windows Server 2019 or newer, current Linux distributions, and upgrades from SQL Server 2014 and above. Database compatibility levels range from 100 to 170.

Does SQL Server IoT 2025 support Fabric mirroring?
Yes. You can mirror operational databases to Fabric without writing ETL. Data flows into OneLake and stays updated in near real time. This keeps the device workload light while letting you centralize analytics.

Can SQL Server IoT 2025 run in containers?
Yes. It works in the same container images as SQL Server 2025. You also get the Linux improvements such as TLS 1.3 support and tmpfs for tempdb-heavy workloads.

Does Arrow have more information on SQL Server IoT 2025?
Yes. Please learn more about SQL Server IoT 2025 here.

Ken Marlin
Ken Marlin
Supplier Manager

Based in Phoenix Arizona, Ken is a Microsoft Business Development Manager at Arrow Electronics. Ken is a 3-time Microsoft MVP on Windows IoT products and has over 35 years of experience in supporting all Microsoft products and channels. Known in the industry as the Windows Champ, Ken has a youtube channel that provides valuable information on getting started with Windows IoT products and “How To” informational videos. His specialty is helping customers with complex licensing on Windows Server, SQL Server and Windows 10 IoT Enterprise.

Get In Touch