hybrid
19 TopicsAnnouncing SQL Server 2025 Preview Support on Ubuntu 26.04 LTS
We are excited to announce preview support for SQL Server 2025 on Ubuntu 26.04 LTS, starting with SQL Server 2025 CU11. This brings SQL Server 2025 to Canonical's latest long-term support release, giving developers and organizations an opportunity to evaluate SQL Server on a modern Ubuntu platform. Alongside this announcement, this blog covers: how to install SQL Server 2025 on Ubuntu 26.04, and the simplified Azure deployment experience for SQL Server on Linux Azure VMs. Preview note: SQL Server 2025 support on Ubuntu 26.04 is currently in preview and is intended for evaluation and testing, not production workloads. Supported platforms and package availability continue to evolve - always check the Release notes for SQL Server on Linux for the latest supported OS matrix. Why Ubuntu 26.04 support matters Organizations increasingly standardize their infrastructure on long-term support (LTS) operating system releases to maintain consistency across their environments. With SQL Server 2025 support on Ubuntu 26.04, you can begin evaluating your database workloads on Canonical's latest LTS release while taking advantage of improvements in the underlying operating system. SQL Server 2025 also introduces capabilities such as native vector search and external AI model integration, enabling developers to build modern AI-enabled applications using their existing SQL Server data. This preview provides an opportunity to validate application compatibility, evaluate deployment configurations, and prepare for future adoption. One SQL Server engine across deployment environments SQL Server provides a consistent core database engine across Windows and Linux, allowing organizations to use familiar database capabilities and tools across different environments. SQL Server on Linux can be deployed on physical servers, virtual machines, and supported container platforms, giving customers flexibility in how they manage their database infrastructure. Ubuntu 26.04 preview support expands the operating system options available for evaluating SQL Server 2025. Installing SQL Server 2025 on Ubuntu 26.04 You can install SQL Server 2025 directly on an Ubuntu 26.04 machine, whether it is running on Azure, another cloud platform, or on-premises. The installation follows the familiar SQL Server on Ubuntu workflow: configure the Microsoft package repository, install SQL Server, and complete the initial setup. Step 1: Import Microsoft’s GPG key First, install the required utilities and import Microsoft's package signing key. # Ensure curl is available, then import the Microsoft signing key sudo apt-get update && sudo apt-get install -y curl curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor -o /usr/share/keyrings/microsoft-prod.gpg Step 2: Register the SQL Server 2025 repository Note: The Ubuntu 26.04 package repository configuration is temporarily unavailable, and we are working on a resolution. In the meantime, you can continue using the container image: mcr.microsoft.com/mssql/server:2025-CU11-ubuntu-26.04-preview Configure the Microsoft package repository for SQL Server 2025 on Ubuntu 26.04. # Register the SQL Server 2025 repo for Ubuntu 26.04 curl -fsSL https://packages.microsoft.com/config/ubuntu/26.04/mssql-server-preview.list | sudo tee /etc/apt/sources.list.d/mssql-server-peview.list Step 3: Install SQL Server 2025 Update the package index and install the SQL Server engine. sudo apt-get update sudo apt-get install -y mssql-server Step 4: Configure SQL Server Run the SQL Server configuration utility to select your edition, accept the license terms, and configure the system administrator password. # Choose edition, accept the license terms, set the SA password sudo /opt/mssql/bin/mssql-conf setup # Verify the service is running systemctl status mssql-server --no-pager Step 5: Install SQL Server command-line tools (optional) You can also install the SQL Server command-line utilities, including sqlcmd and bcp. First, register the Microsoft production repository. # Add the prod repo, then install sqlcmd / bcp (mssql-tools18) curl -fsSL https://packages.microsoft.com/config/ubuntu/26.04/prod.list | sudo tee /etc/apt/sources.list.d/mssql-release.list sudo apt-get update sudo apt-get install -y mssql-tools18 unixodbc-dev That’s it. With SQL Server 2025 installed on Ubuntu 26.04, you can connect using familiar tools such as SQL Server Management Studio (SSMS), the MSSQL extension for Visual Studio Code, or sqlcmd. You can now begin exploring SQL Server 2025 capabilities and validating your applications on Ubuntu 26.04. Simplifying SQL Server on Linux deployments in Azure In addition to expanding operating system support, we've introduced a more flexible way to deploy SQL Server on Linux Azure Virtual Machines. Traditionally, customers deployed SQL Server on Linux using preconfigured Azure Marketplace images that included both the operating system and SQL Server. The new script-based deployment experience simplifies this approach by allowing customers to provision a Linux VM and configure SQL Server as part of the deployment process. Instead of relying on a preconfigured SQL Server image, customers can start with a supported Linux operating system image and select their SQL Server configuration. How script-based deployment works If you prefer a SQL-first deployment experience, the Azure SQL hub provides a streamlined way to deploy SQL Server on Linux Azure VMs. Go to the Azure SQL hub at aka.ms/azuresqlhub. Under SQL Server, select SQL Server on Azure VMs, and then select + Create. Select the operating system for your deployment. You will be redirected to the Create a virtual machine experience. Your operating system selection is automatically carried forward, and Install SQL Server option is enabled by default under the Advanced tab. Configure the remaining VM and SQL Server settings. You can also use advanced configuration to upload a custom mssql.conf file, configure SQL connectivity, enable Azure Key Vault integration, and the tuned performance profile. Select Review + create, review the configuration summary, and then select Create. Azure provisions the VM, installs and configures SQL Server through the same script-based deployment flow, and automatically registers the VM with the SQL IaaS Agent extension. Getting started & reference Install on Ubuntu: Quickstart: Install SQL Server and create a database on Ubuntu Installation guidance: Installation guidance for SQL Server on Linux Supported platforms: Release notes for SQL Server on Linux Containers: Deploy and connect to SQL Server Linux containers SQL IaaS Agent extension (Linux): Overview · Register a Linux SQL Server VM Wrapping up Preview support for SQL Server 2025 on Ubuntu 26.04 LTS marks another step in expanding deployment flexibility for SQL Server on Linux. Together with the new script-based deployment experience on Azure VMs and integration with the SQL IaaS Agent extension, customers have more options to deploy and manage SQL Server on Linux. We encourage you to explore SQL Server 2025 on Ubuntu 26.04 in your test environments and share your feedback to help us continue improving the experience.42Views2likes0CommentsStrengthen SQL Server security on Azure Local with confidential VMs (In Preview)
SQL Server holds some of the most sensitive data an organization runs, including the business data that local AI applications and agents query. Azure Local provides a Microsoft-managed, distributed infrastructure platform for running SQL Server in virtual machines at customer locations, so data can stay on premises. Data at rest and in transit is commonly protected, but while SQL Server processes queries, the data it works with sits in memory. Confidential virtual machines (CVMs) on Azure Local help protect it there. Protecting SQL Server requires more than securing the database engine. With a standard VM, the host operating system, the hypervisor, and anyone with administrative access to the host all sit inside the trust boundary of the workload. At edge and remote sites with less physical control, that is a lot of trust to place in the infrastructure. CVMs on Azure Local, now generally available on AMD processors and in preview on Intel processors, bring hardware-based memory encryption and attestation to customer-owned edge infrastructure. They provide hardware-based isolation between the VM, the hypervisor, and host management code. SQL Server 2025 runs on Ubuntu 24.04 inside the CVM. For SQL Server workloads, the value is straightforward: help keep data confidential while it is in use, even from the infrastructure it runs on. Where confidential VMs fit Consider CVMs when SQL Server data should stay private from the people and systems that operate on the underlying infrastructure, such as regulated and sovereign data, edge and remote sites, hosted or partner-run clusters, and local AI applications that query sensitive business data. Protect SQL Server data while it is in use CVMs on Azure Local use AMD SEV-SNP or Intel TDX to encrypt guest memory in hardware, so SQL Server's buffer pool and in-memory data stay encrypted and isolated from the host and its administrators. CVMs don't protect against sophisticated physical side-channel attacks, so pair them with physical safeguards at the site. Data on disk, in backups, and in transit still needs SQL Server's own protections. The following table shows how they fit together. What you're protecting Threat Protection SQL Server memory, including the buffer pool Host administrators or a compromised host CVM memory encryption (AMD SEV-SNP or Intel TDX) Operating system disk and boot chain Host-side tampering Integrity-protected image Data, log, and tempdb files A copy of the data disk taken from the host TDE with keys in Azure Key Vault Backups Copies stored outside the VM Backup encryption Network traffic Interception between clients and SQL Server Encrypted connections (TLS) Sensitive columns Privileged database users Always Encrypted Start from an integrity-protected image CVMs follow a clean-room, image-driven model. You build a hardened Ubuntu 24.04 image with SQL Server 2025 installed and enable integrity protection, which helps protect the guest operating system disk and boot chain from host-side tampering. The root file system is read-only, so SQL Server databases, logs, and tempdb live on a separate writable data disk. To maintain the security boundary, guest management isn't supported, so plan guest changes, including SQL Server updates, as new image builds rather than in-place changes. Plan availability around confidential VMs CVMs don't support live migration or failover between nodes in an Azure Local cluster, so plan maintenance around the CVMs on each node, build availability into the database design, and keep regular SQL Server backups outside the VM. Verify the environment with attestation Attestation helps you confirm that SQL Server is running in a genuine confidential environment before you trust it with sensitive data. The CVM produces a hardware-rooted attestation report that Microsoft Azure Attestation validates, so plan cloud connectivity from the site. Get started with SQL Server on confidential VMs Prepare a CVM-ready cluster. Deploy Azure Local 2607 or later on validated AMD or Intel hardware with confidential VMs enabled by following the Azure Resource Manager template guidance. Hardware partners for both include Dell, HPE, and Lenovo. Find specific validated systems in the Azure Local solutions catalog. Build the SQL Server image. Use the integrity-protected CVM image builder in the AzureStack-Tools repository to create an Ubuntu 24.04 image, add SQL Server 2025, and point SQL Server at a separate data disk. Create the confidential VM. Create the CVM from your image with the data disk attached by following the CVM creation and connection guidance. Verify and connect. Verify the CVM with attestation and connect your applications. For detailed guidance, see Deploy SQL Server on Azure Local. Review the confidential VM overview for current limitations. Frequently asked questions How is this different from Always Encrypted? Always Encrypted protects selected columns from anyone without the column keys, including database administrators. A CVM protects all of SQL Server's memory from the host and infrastructure operators. They address different threats, so use both when you need protection from both groups. Can I convert an existing VM into a confidential VM? No. CVMs are created from a purpose-built, integrity-protected image. Create a new CVM and move your databases into it with backup and restore. Does it support SQL Server on Windows? Not yet. This release supports Ubuntu 24.04 guests only. A stronger foundation for sensitive database workloads When SQL Server runs in a confidential VM on Azure Local, its memory is encrypted and isolated from the host, the hypervisor, and infrastructure operators, and attestation provides evidence of that protection before applications connect. That brings confidential computing to SQL Server workloads that need to stay on premises.30Views2likes0CommentsYour day-by-day guide to Microsoft SQL at Ignite 2026
Microsoft Ignite returns to San Francisco November 17–20, bringing together developers, data professionals, and technology leaders. Whether you’re modernizing an existing SQL estate or building your next AI application, our sessions offer a practical path through the week—from architecture and migration decisions to hands-on development. Here’s what to add to your agenda. Tuesday, November 17: Bring AI and agents closer to your data Start with No Cloud Required: Build AI apps with SQL Server on Azure Local (BRK450). Join Bob Ward as he explores how to bring SQL and local AI to sovereign, regulated, edge, and disconnected environments while keeping sensitive data within trusted boundaries. Then join Less Hunting, More Building: Database Agents in a Unified Estate (BRK363). See how Database Hub and database agents can help teams surface issues, understand likely causes, and act with human approval using familiar SQL tools. Onsite? Make sure you join us in the Hub and look for the AMD booth during the evening recaption for an exclusive book signing for Bob Ward’s latest book “SQL Hyperscale Unveiled” Wednesday, November 18: Build the foundation—and go deeper Start your day with Data foundations for modern apps, AI, and agents (BRK362). Join Shireesh Thota together with leaders across Azure Databases as they share how operational, analytical, relational, and NoSQL platforms work together to support modern applications and agents. Follow that up by going deeper into SQL’s cloud-native offering Hyperscale in Humans to agents: Mission-critical starts with Azure SQL Hyperscale with Bob Ward and Anna Hoffman. This session is designed to explore the architecture, scale, resilience, and AI capabilities behind production-ready applications. Short on time? Catch Data modernization decision tree for growing businesses* a 15min lightning talk with Bob Ward, for a practical guide at SQL Server migration choices, Learn how to Ship database changes faster with agents in Database Hub or bring your questions and join the conversation with VP of SQL Priya Sathy at our table talk, spots are limited, so make sure you add it to you schedule and get there early. Thursday, November 19: Choose your architecture and build what’s next Not all applications are created equal, which makes choosing the right database critical. But how do you cut through the noise and pick the right solution for your application workloads? Database SOS: Choosing the right engine for your job will help teams weigh the options across Azure’s database portfolio. Or maybe SaaS deployments are more your speed? Join Anna as she shares how to ground your agents on operational data and connect your agentic applications to analytics in one platform in: Where agents meet analytics: Build with SQL Database in Fabric. Why run SQL on Azure? Priya Sathy, VP of SQL, shows you in a demo-heavy session on what sets Azure apart as your data platform for modern, AI-ready apps: Why Azure is the best cloud for SQL. Close out your day with Bob and Anna as they pull back the curtains and share the SQL roadmap, see what’s next in Sneak peek: What's next in SQL. Friday, November 20: Simplify your DevOps Close the week with BRK373, Build AI-ready apps on Azure SQL with GitHub Copilot in VS Code. Follow an application from local prototype through database design, retrieval-augmented generation, API creation, and cloud deployment. All week: Go one step further with technical skilling Lab Building search for AI apps and agents with Azure SQL Database, is planned across multiple days, including Friday. Check the schedule builder for its available lab times and to confirm your final agenda. From SQL Server and Azure Local to Azure SQL Database, Hyperscale, and SQL database in Fabric, there’s a session for wherever you are in your data journey. Explore the full Ignite schedule and we’ll see you there!323Views1like0CommentsAnnouncing flexible provisioning for SQL Server on Linux Azure VMs (Public Preview)
What’s changing We’re introducing a new script-based deployment experience for provisioning SQL Server on Linux Azure Virtual Machines (VMs). This experience replaces the earlier model that relied on pre-created SQL Server on Linux Marketplace images, which have been deprecated. Pre-created SQL Server on Linux Marketplace images are no longer available for new provisioning through the Azure portal, the Azure SQL hub, Azure CLI, or PowerShell. Instead, SQL Server is now installed and configured during VM provisioning using a flexible, automated, script-based workflow. The result is a more adaptable and supportable deployment model that keeps SQL Server on Linux Azure VMs fully supported, reduces image-maintenance overhead, and makes it easier to adopt the latest Linux distributions, VM families, and configuration options - all while giving you more control over your SQL Server setup. Why the new model matters Greater flexibility and control — choose your Linux distribution, SQL Server version, edition, and even bring your own mssql.conf to tailor the configuration. Faster access to innovation — new Linux versions and Azure capabilities are picked up automatically, without waiting for a new baked image to be published. Automatic registration built in — every VM is registered with the SQL IaaS Agent extension by default, unlocking licensing flexibility, compliance, and richer visibility. A dynamic, guided UI — the portal enables or disables options based on supported operating system, SQL Server, and licensing combinations, so you only see valid choices. Supported Linux distributions The script-based deployment experience supports the following distributions, and future versions are picked up automatically as they become supported — no manual intervention required: Distribution Supported versions Red Hat Enterprise Linux (RHEL) RHEL 9, RHEL 10 (and future versions) Ubuntu Ubuntu 22.04, Ubuntu 24.04, Ubuntu 26.04 (and future versions) Automatic registration applies to both Red Hat Enterprise Linux and Ubuntu, across all their supported versions. Automatic registration with the SQL IaaS Agent extension SQL Server on Linux VMs deployed through this experience are automatically registered with the SQL Server IaaS Agent extension. Registration creates a SQL virtual machine resource in Azure (separate from the VM resource) and unlocks: Licensing flexibility — choose Pay-As-You-Go (PAYG) or Azure Hybrid Benefit (AHB), and switch between them anytime with no downtime. Compliance — a simplified way to meet Azure Hybrid Benefit product-term requirements without per-resource registration forms. Visibility and telemetry — clear license-type visibility, subscription-level tracking, and better operational insight from the Azure portal, CLI, or PowerShell. Note: Automatic registration is enabled by default during deployment. You can unregister or re-register a VM after deployment through the Azure portal, Azure CLI, or PowerShell. The end-to-end flow at a glance Two ways to deploy You can provision SQL Server on Linux through either of these Azure portal experiences. Both lead to the same guided SQL Server configuration: Create a virtual machine tab - start from the standard Azure VM creation flow and add SQL Server. Azure SQL hub (aka.ms/azuresqlhub) - start from a SQL-first experience with SQL Server on Azure VMs. Experience 1: The “Create a virtual machine” tab Use this flow if you prefer to start from the standard VM creation experience in the Azure portal. In the Azure portal, go to Virtual machines (or Create a resource → Virtual machine) and select Create. On the Basics tab, select your project details (subscription, resource group), instance details, and a supported Linux base image — RHEL 9, RHEL 10, Ubuntu 22.04, or Ubuntu 24.04. Choose your VM size, authentication, and inbound ports as usual. Go to the Advanced tab and select the Install SQL Server checkbox. This enables SQL Server provisioning on the VM. A new SQL Server settings tab becomes available. Open it to configure your SQL Server deployment: SQL Server version — e.g., SQL Server 2025 or SQL Server 2022. Edition — Enterprise, Standard, Developer, Express, and Evaluation editions (options adjust to the selected version). Licensing model — Pay-As-You-Go (PAYG, default) or Azure Hybrid Benefit (AHB). Advanced configuration — Upload a custom mssql.conf file to set SQL connectivity, Azure Key Vault integration, and the tuned performance profile. Select Review + create, review the configuration summary, and select Create. Azure provisions the VM, then automatically installs and configures SQL Server and registers the VM with the SQL IaaS Agent extension. Experience 2: Azure SQL hub Use this flow if you prefer a SQL-first experience, where SQL Server on Linux is available as a first-class deployment option. Go to the Azure SQL hub at aka.ms/azuresqlhub. Under SQL Server, select SQL Server on Azure VMs, and then select + Create. Select the operating system for your deployment. You’re seamlessly transitioned to the Create a virtual machine experience. Your operating system selection is automatically carried forward, and Install SQL Server is enabled on the Advanced tab. Configure the remaining VM and SQL Server settings, including size, networking, disks, licensing, connectivity, Key Vault integration, tuned profile, or a custom mssql.conf. Select Review + create, review the configuration summary, and then select Create. Azure provisions the VM, installs and configures SQL Server through the same script-based deployment flow, and automatically registers the VM with the SQL IaaS Agent extension. Managing licensing after deployment Because your VM is registered with the SQL IaaS Agent extension, you can change the licensing model anytime — with no downtime and no restart of the VM or SQL Server service. Azure portal: Go to the SQL virtual machine resource → Settings → SQL Server configuration → Manage. Azure CLI az sql vm update -n <VM_NAME> -g <RESOURCE_GROUP> --license-type AHUB Azure PowerShell: Set-AzSqlVM -Name <VM_NAME> -ResourceGroupName <RESOURCE_GROUP> -LicenseType AHUB Note: Switching between PAYG and AHB is immediate, incurs no additional cost, and does not restart the VM or the SQL Server service. Wrapping up The move to script-based deployment modernizes how you provision SQL Server on Linux Azure VMs. By replacing deprecated pre-created Marketplace images with a flexible, automated, script-based flow — and by registering every VM with the SQL IaaS Agent extension automatically — you get more choice, faster access to new Linux and SQL Server versions, and a cleaner path to licensing flexibility, compliance, and visibility. Whether you start from the Create a virtual machine tab or the Azure SQL hub, you get the same guided experience across RHEL 9, RHEL 10, Ubuntu 22.04, Ubuntu 24.04, and future versions. Ready to try it? Head to a Create a virtual machine option in the Azure portal. We’d love your feedback — let us know how the new experience works for your workloads in the comments.395Views1like0CommentsMicrosoft at PASS Data Community Summit 2026:
Microsoft is excited to be back as Sapphire Sponsor and bring that spirit to life through a mix of technical deep dives, community-led conversations, and opportunities to engage directly with Microsoft product leaders and experts. This year, we’ll go deep across the Azure Data portfolio to cover the subjects we’ve been asked about the most, from SQL, PostgreSQL, to Fabric. Whether you’re talking SQL over breakfast, asking your toughest questions during our Azure Data AMA, diving deep with the engineers building the products you use every day, or catching a live Data Exposed session, there are plenty of ways to participate beyond the breakout room. PASS Data Community Summit is more than a place to hear what’s new. It’s a place to be part of what’s next. Microsoft together with our co-sponsor AMD will be there with sessions and experiences that will hopefully leave you inspired by what you can build next. Here’s a look at the Microsoft sessions happening across the week: But PASS Data Community Summit has always been more than just sessions. So, we’re bringing back some of the most popular experiences to the community: We hope to see you there! Register now and use code AZURE150 for a discount off your registration!270Views1like0CommentsMove to Modern SQL Server Licensing with Confidence
Why eligible customers should move to pay-as-you-go licensing (PAYG) For eligible SQL Server workloads, PAYG should be the preferred licensing approach when moving away from licenses and Software Assurance. It aligns billing with measured usage, adapts as the estate changes, and reduces the operational burden of managing fixed license quantities. The transition requires deliberate resource-configuration updates, but the result is a more flexible and manageable licensing model. Align cost with measured usage: Adopt consumption-based billing for eligible SQL Server resources instead of maintaining fixed license allocations. Scale without repeated license true-ups: Let billing adjust as workloads are added, removed, migrated, resized, or used intermittently. Manage licensing through Azure: Use Azure-based controls to review resource-level licensing and improve visibility across the estate. Reduce license administration: Spend less time tracking fixed quantities and aligning individual resources with license inventory. Optimize committed consumption: After establishing stable PAYG usage, evaluate applicable Azure savings plans or reservations to help reduce costs. Guidance for transitioning your resource settings Once your organization decides to adopt PAYG for eligible SQL Server workloads, update the license configuration on each resource so billing reflects that decision. A commercial or licensing change alone does not update resource-level settings. Plan this configuration work as part of the transition rather than treating it as a follow-up. Starting early gives teams time to validate security, networking, Azure Arc connectivity, billing, and operational processes before switching the broader estate. Automate the transition to pay-as-you-go SQL licensing at scale Choose the transition approach that fits your estate PowerShell for a controlled bulk change Use PowerShell when you need a targeted transition across a defined tenant, subscription, resource group, or resource scope. Discover and review resources before making changes. Test the transition with a limited scope. Update eligible resources in bulk when the organization is ready. Validate the resulting license configuration and billing signals. Azure Policy for ongoing governance Use Azure Policy to transition existing SQL resources to PAYG and continuously enforce the desired licensing configuration. Azure Policy helps identify configuration drift, maintain compliance, and automatically remediate non-compliant resources at scale. Define the approved license configuration for eligible resources. Assign policy at the appropriate subscription or resource group scope. Monitor compliance through centralized Azure views. Remediate resources that drift from the approved configuration. Recommended path to PAYG Commit to the PAYG target. Confirm which eligible workloads will move and identify the teams responsible for licensing, Azure, security, networking, and SQL operations. Prepare the estate. For SQL Server running outside of Azure, connect to Azure Arc. Inventory eligible SQL resources and confirm that Azure Arc connectivity and required organizational approvals are in place. Prove the transition. Test resource updates and billing behavior in a limited resource group or subscription. Move at scale. Use PowerShell for a controlled bulk transition, then apply Azure Policy for ongoing governance where appropriate. Verify and operate. Review the resulting configuration, monitor compliance, and reassess as the SQL estate grows or changes. Evaluate commitment-based savings. After establishing a stable PAYG usage pattern, assess whether an applicable Azure savings plan or reservation could reduce costs. Review eligibility, coverage, and commitment terms with your Microsoft representative. Learn more Automate the transition to pay-as-you-go SQL licensing at scale Manage licensing and billing of SQL Server enabled by Azure Arc Pricing guidance for SQL Server on Azure VMs Azure SQL Database pricing Eligibility, billing treatment, prerequisites, and available licensing options vary by resource and licensing arrangement. Review the applicable Microsoft terms and product guidance, and consult your Microsoft representative or licensing specialist as needed.977Views0likes2CommentsSQL Server 2016 Extended Security Updates: Stay Protected While You Modernize
SQL Server 2016 reaches the end of extended support on July 14, 2026. After that date, instances that remain on SQL Server 2016 no longer receive regular security updates unless they are covered through Extended Security Updates (ESUs)). ESUs provide a time-bound security bridge for customers who need to maintain existing workloads while they upgrade to a supported SQL Server release or modernize to Azure SQL. SQL Server 2016 Extended Security Updates can be managed across multiple deployment models, including SQL Server enabled by Azure Arc for on-premises and other clouds, and SQL Server on Azure Virtual Machines. This provides a consistent protection path while customers assess modernization options and operational readiness. Today, we are making the Extended Security Updates subscription experience available in Azure so customers can enroll ahead of SQL Server 2016 reaching end of support, and be ready to receive Extended Security Updates when they are released. Why this matters now SQL Server follows a fixed lifecycle policy with mainstream support followed by extended support. Once SQL Server 2016 exits extended support, Extended Security Updates become the only for continued security coverage on that version. Extended Security Updates are intended as a temporary option for risk reduction, not as a long-term alternative to upgrade or modernization. For many production environments, the constraint is not awareness of the deadline but the complexity of the upgrade path. Application dependencies, validation requirements, change windows, and compliance controls sometimes make immediate migration impractical. Extended Security Updates help teams maintain security coverage during that transition period while they sequence remediation, testing, and platform changes. How SQL Server 2016 Extended Security Updates work Support window: SQL Server 2016 exits extended support on July 14, 2026. Extended Security Updates are available for up to three additional years, with coverage periods defined by the SQL Server 2016 lifecycle schedule through July 17, 2029. Supported scope and update model Eligible versions: SQL Server 2016. Extended Security Updates are also available for SQL Server 2014 until July 12, 2027. Eligible editions: Standard and Enterprise Update content: Extended Security Updates deliver critical security updates when applicable. They do not include new features, non-security bug fixes, non-critical security updates, or design changes. Operational note: SQL Server ESUs are not published on a fixed monthly cadence. They are released when qualifying vulnerabilities require a release. For Azure Arc-connected environments, Extended Security Updates subscriptions can be aligned to the deployment model, including virtual cores for VM-based deployments and physical cores for host-based scenarios. This gives organizations flexibility to match ESU coverage to how SQL Server is deployed and managed. How to acquire Extended Security Updates coverage Customers can acquire SQL Server ESU coverage in different ways depending on where SQL Server is running and how they prefer to purchase. For on-premises, edge, and other cloud environments, SQL Server enabled by Azure Arc provides the control plane to onboard instances, manage eligibility, and apply ESU subscription settings. For workloads already running on Azure Virtual Machines, customers can subscribe to ESU coverage through Azure-based controls. Customers can purchase that coverage as pay-as-you-go through Azure or through Volume Licensing on an annual basis for eligible licenses with active Software Assurance. When customers choose Volume Licensing, Azure Arc registration is still required to activate access to ESUs. SQL Server enabled by Azure Arc: Use Azure Arc to onboard eligible SQL Server instances outside Azure, manage Extended Security Updates subscription settings, and support both connected and qualifying disconnected scenarios. SQL Server on Azure Virtual Machines: Use Azure-based controls to subscribe to Extended Security Updates coverage for workloads running on Azure Virtual Machines. For SQL Server 2016, this now requires a paid ESU subscription rather than the previous no-additional-cost experience. Supported regions: Subscribing to Extended Security Updates for SQL Server on Azure VMs is only available in the supported regions listed. To subscribe to ESUs in an unsupported region, contact Microsoft Support to determine the appropriate ESU acquisition path. Volume Licensing: If you cannot subscribe to Extended Security Updates via Azure Arc, you can purchase through the Volume Licensing channel on an annual basis for eligible licenses with active Software Assurance. Talk to your Microsoft seller for more information. Azure Arc registration is still required to activate access to ESUs. Migrate to Azure SQL: Customers that are ready to modernize further can move to Azure SQL Database or Azure SQL Managed Instance, which removes Extended Security Updates dependency by moving to fully supported, cloud-managed SQL services. The following diagram summarizes how customers can obtain SQL Server 2016 Extended Security Updates coverage through Azure Arc and Azure Virtual Machines. What to do next Organizations still running SQL Server 2016 should use the remaining support window to assess estate readiness, determine the right Extended Security Updates subscription model, and define the target modernization path for each workload. For some environments, that means upgrading in place to a supported SQL Server version. For others, it means migrating and upgrading to Azure Virtual Machines or Azure SQL to simplify long-term operations. The important step is to make the transition plan executable before support ends. Learn more SQL Server end of support options SQL Server Extended Security Updates enabled by Azure Arc SQL Server enabled by Azure Arc Extend support for SQL Server with Azure VM SQL Server on Azure VM overview Migrate to Azure SQL5.3KViews0likes7CommentsUnlocking Enterprise AI: SQL Server 2025 and NVIDIA Nemotron RAG Accelerate AI
Today, most of the world’s data still remains untapped, sitting in databases, documents, and systems across organizations. Enterprises are racing to unlock this data’s value by building the next wave of generative AI applications—solutions that can answer questions, summarize documents, and drive smarter decisions. At the heart of these innovations are retrieval-augmented generation (RAG) pipelines, which enable users to interactively engage with large amount of data that continuously evolves. Yet, as promising as RAG pipelines are, enterprises face real challenges in making them work at scale. Handling both structured and unstructured data, processing massive volumes efficiently, and ensuring privacy and security are just a few hurdles. This is where the integration between SQL Server 2025 and NVIDIA Nemotron RAG models, deployed as NVIDIA NIM microservices, comes in, offering a new approach that streamlines AI deployment and delivers enterprise-grade performance—whether you’re running workloads in the cloud or on-premises. “As AI becomes core to every enterprise, organizations need efficient and compliant ways to bring intelligence to their data,” said Joey Conway, Senior Director of Generative AI software at NVIDIA. “With SQL Server 2025’s built-in AI and NVIDIA Nemotron RAG, deployed as NIM microservices, enterprises can deploy and run AI models close to their data on premises or in the cloud without complex integration, accelerating innovation while maintaining data sovereignty and control.” Overcoming the complexity of generating embeddings at scale Customer challenge Building responsive AI applications using RAG requires converting SQL data into vector embeddings—a process that feeds huge amounts of text through complex neural networks. This is inherently parallel and compute-intensive, often creating performance bottlenecks that prevent real-time data indexing. The result? Slow applications and poor user experiences. Moreover, enterprises need flexibility. Different embedding models excel at different tasks—semantic search, recommendations, classification—and each comes with its own tradeoffs in accuracy, speed, and cost. Businesses want to mix and match models, balance premium performance with budget constraints, and stay resilient against model deprecation or API changes. Furthermore, rapid experimentation and adaptation are key to staying ahead and thus developers want models that offer flexible customization and full transparency. The Solution: SQL Server 2025 + NVIDIA Nemotron RAG SQL Server 2025 brings AI closer to your data, allowing you to natively and securely connect to any model hosted anywhere. You can generate embeddings directly in SQL using extensions to T-SQL —no need for new languages, frameworks, or third-party tools. By connecting SQL Server 2025 to the llama-nemotron-embed-1b-v2 embedding model from NVIDIA, you eliminate bottlenecks and deliver the massive throughput needed for real-time embedding generation. llama-nemotron-embed-1b-v2 is a best in class embedding model that offers multilingual and cross-lingual text question-answering retrieval with long context support and optimized data storage. This model is part of NVIDIA Nemotron RAG models, a collection of extraction, embedding, reranking models, fine-tuned with the Nemotron RAG datasets and scripts, to achieve the best accuracy. These models offer flexible customization, enabling easy fine-tuning and rapid experimentation. They also offer full transparency with open access to models, datasets, and scripts. Llama-nemotron-embed-1b-v2 is the model of choice for embedding workflows, but this high-speed inference pipeline is not limited to this model and can potentially call any optimized AI model as an NVIDIA NIM microservice, seamlessly powering every stage of the RAG pipeline. From multimodal data ingestion and advanced retrieval to reranking, all operations run directly on your data within SQL Server. Such RAG systems can be applied across a wide range of use cases, enabling intelligent, context-aware applications across industries. Customer Benefits: With GPU acceleration and built-in AI of SQL Server 2025, you can achieve optimal inference, ensuring performance that meets the demands of modern applications. Our flexible approach lets you mix and match models to suit different use cases, striking the right balance between accuracy and cost. And with open models that enable vendor flexibility and rapid adaptation, you gain resilience to stay ahead of the curve in an ever-changing AI landscape. Streamlining AI Model Deployment with Enterprise-Grade Confidence Customer Challenge Integrating advanced AI models into enterprise workflows has historically been slow and complex. Specialized teams must manage intricate software dependencies, configure infrastructure, and handle ongoing maintenance—all while navigating the risks of deploying unsupported models in mission-critical environments. This complexity slows innovation, drains engineering resources, and increases risk. The Solution: Simplified, Secure Model Deployment with NVIDIA NIM This collaboration simplifies and de-risks AI deployment. The llama-nemotron-embed-1b-v2 model is available as an NVIDIA NIM microservice for secure, reliable deployment across multiple Azure compute platforms. Prebuilt NIM containers for a broad spectrum of AI models and can be deployed with a single command for easy integration into enterprise-grade AI applications using built-in REST APIs of SQL Server 2025 and just a few lines of code, regardless where you run SQL Server workloads and NVIDIA NIM, on premises or in the cloud. NIM containers package the latest AI models together with the best inference technology from NVIDIA and the community and all dependencies into a ready-to-run container, abstracting away the complexity of environment setup so customers can spin up AI services quickly. Furthermore, NVIDIA NIM is enterprise-grade and is continuously managed by NVIDIA with dedicated software branches, rigorous validation processes, and support. As a result, developers can confidently integrate state-of-the-art AI into their data applications. This streamlined approach significantly reduces development overhead and provides the reliability needed for mission-critical enterprise systems. NVIDIA NIM containers are discoverable and deployable via Microsoft Azure AI Foundry’s model catalog. Customer Benefits Rapid deployment with minimal setup means you can start leveraging AI without specialized engineering, and SQL Server 2025 makes it even easier with built-in support for AI workloads and native REST APIs. Enterprise-grade security and monitoring ensure safe, reliable operations, while SQL Server’s integration with Entra ID and advanced compliance features provide added protection. Direct integration into SQL workflows reduces complexity and risk, and with SQL Server’s hybrid flexibility, you can run seamlessly across on-premises and cloud environments—simplifying modernization while maintaining control. Innovating Without Compromise on Security or Flexibility Customer Challenge Organizations in regulated industries often face a tough choice: adopt powerful AI or maintain strict data residency and compliance. Moving sensitive data to external services is often not an option, and many companies run AI inference workloads both in the cloud and on-premises to balance scalability, privacy, regulatory compliance, and low-latency requirements. The Solution: Flexible, Secure Integration—On-Premises and Cloud SQL Server 2025 enables organizations in regulated environments to securely integrate locally hosted AI models, ensuring data residency and compliance while minimizing network overhead. This architecture boosts throughput by keeping sensitive data on-premises and leveraging SQL Server’s native extensibility for direct model invocation. With SQL Server 2025 and Nemotron RAG, deployed as NVIDIA NIM microservices, you get the best of both worlds. This solution can be seamlessly deployed in the cloud with serverless NVIDIA GPUs on Azure Container Apps (ACA) or on-premises with NVIDIA GPUs on Azure Local. Sensitive data never leaves your secure environment, allowing you to harness the full power of Nemotron models while maintaining complete data sovereignty and meeting the strictest compliance mandates. Customer Benefits SQL Server 2025 helps you maintain compliance by supporting data residency and meeting regulatory standard requirements across regions. Sensitive data stays protected on-premises with enterprise-grade security, including consistent access controls, ledger support, and advanced encryption to minimize risk. At the same time, SQL Server’s hybrid flexibility lets you deploy AI workloads wherever they’re needed—on-premises, in the cloud, or across a hybrid environment—while leveraging built-in AI features like vector search and secure integration with locally hosted models for performance and control. Conclusion: Powering the Next Wave of Enterprise AI The collaboration between Microsoft and NVIDIA is more than a technical integration. It’s designed to help enterprises overcome the toughest challenges in AI deployment. By streamlining vector embedding and vector search, delivering enterprise-grade performance, and enabling secure, flexible integration across cloud and on-premises environments, this joint solution empowers organizations to unlock the full value of their data. Whether you’re building conversational AI, automating document analysis, or driving predictive insights, SQL Server 2025 and NVIDIA Nemotron RAG models, deployed as NIM, provide the tools you need to innovate with confidence. The future of enterprise AI is here and it’s flexible, secure, and built for real business impact. Get started today: Learn more about SQL Server 2025 and download it today Learn more about our joint solution from NVIDIA’s Technical Blog GitHub: Microsoft SQL Server 2025 and NVIDIA Nemotron RAG1.8KViews1like0Comments