Introducing the Azure SQL hub: A simpler, guided entry into Azure SQL
Choosing the right Azure SQL service can be challenging. To make this easier, we built the Azure SQL hub, a new home for everything related to Azure SQL in the Azure portal. Whether you’re new to Azure SQL or an experienced user, the hub helps you find the right service quickly and decide, without disrupting your existing workflows. For existing users: Your current workflows remain unchanged. The only visible update is a streamlined navigation pane where you access Azure SQL resources. For new users: Start from the Azure SQL hub home page. Get personalized recommendations by answering a few quick questions or chatting with Azure portal Copilot. Or compare services side by side and explore key resources, all without leaving the portal. This is one way to find it: Searching for "azure sql" in main search box or marketplace is also efficient way to get to Azure SQL hub Answer a few questions to get our recommendation and use Copilot to refine your requirements. Get a detailed side-by-side comparison without leaving the hub. Still deciding? Explore a selection of Azure SQL services for free. This option takes you straight to the resource creation page with a pre-applied free offer. Try the Azure SQL hub today in the Azure portal, and share your feedback in the comments!Convert geo-replicated databases to Hyperscale
We’re excited to introduce the next improvement in Hyperscale conversion: a new preview feature that allows customers to convert Azure SQL databases to Hyperscale by keeping active geo-replication or failover group configurations intact. This builds on our earlier improvements and directly addresses one of the most requested capabilities from customers. With this improvement, customers can now modernize your database architecture with Hyperscale while maintaining business continuity. Overview We have heard feedback from customers about possible improvements we could make while converting their databases to Hyperscale. Customers complained about the complex steps they needed to perform to convert a database to Hyperscale when the database is geo-replicated by active geo-replication or failover groups. Previously, converting to Hyperscale required tearing down geo-replication links and recreating them after the conversion. Now, that’s no longer necessary. This improvement allows customers to preserve their cross-region disaster recovery or read scale-out configurations and still allows conversion to Hyperscale which helps in minimizing downtime and operational complexity. This feature is especially valuable for applications that rely on failover group endpoints for connectivity. Before this improvement, if application needs to be available during conversion, then connection string needed modifications as a part of conversion because the failover group and its endpoints had to be removed. With this new improvement, the conversion process is optimized for minimal disruption, with telemetry showing majority of cutover times under one minute. Even with a geo-replication configuration in place, you can still choose between automatic and manual cutover modes, offering flexibility in scheduling the transition. Progress tracking is now more granular, giving customers better visibility into each stage of the conversion, including the conversion of the geo-secondary to Hyperscale. Customer feedback Throughout the private preview phase, we have received overwhelmingly positive feedback from several customers about this improvement. Viktoriia Kuznetcova, Senior Automation Test Engineer from Nintex says: We needed a low-downtime way to move our databases from the Premium tier to Azure SQL Database Hyperscale, and this new feature delivered perfectly; allowing us to complete the migration in our test environments safely and smoothly, even while the service remained under continuous load, without any issues and without needing to break the failover group. We're looking forward to the public release so we can use it in production, where Hyperscale’s ability to scale storage both up and down will help us manage peak loads without overpaying for unused capacity. Get started The good news is that there are no changes needed to the conversion process. The workflow automatically detects that a geo-secondary is present and converts it to Hyperscale. There are no new parameters, and the method remains the same as the existing conversion process which works for non-geo-replicated databases. All you need is to make sure that: You have only one geo-secondary replica because Hyperscale doesn't support more than one geo-secondary replica. If a chained geo-replication configuration exists, it must be removed before starting the conversion to Hyperscale. Creating a geo-replica of a geo-replica (also known as "geo-replica chaining") isn't supported in Hyperscale. Once the above requirements are satisfied, you can use any of the following methods to initiate the conversion process. Conversion to Hyperscale must be initiated starting from the primary geo-replica. The following table provides sample commands to convert a database named WideWorldImporters on a logical server called contososerver to an 8-vcore Hyperscale database with manual cutover option. Method Command T-SQL ALTER DATABASE WideWorldImporters MODIFY (EDITION = 'Hyperscale', SERVICE_OBJECTIVE = 'HS_Gen5_8') WITH MANUAL_CUTOVER; PowerShell Set-AzSqlDatabase -ResourceGroupName "ResourceGroup01" -ServerName "contososerver" -DatabaseName "WideWorldImporters" -Edition "Hyperscale" -RequestedServiceObjectiveName "HS_Gen5_8" -ManualCutover Azure CLI az sql db update --resource-group ResourceGroup01 --server contososerver --name WideWorldImporters --edition Hyperscale --service-objective HS_Gen5_8 --manual-cutover Here are some notable details of this improvement: The geo-secondary database is automatically converted to Hyperscale with the same service level objective as the primary. All database configurations such as maintenance window, zone-resiliency, backup redundancy etc. remain the same as earlier (i.e., both geo-primary and geo-secondary would inherit from their own earlier configuration). A planned failover isn't possible while the conversion to Hyperscale is in progress. A forced failover is possible. However, depending on the state of the conversion when the forced failover occurs, the new geo-primary after failover might use either the Hyperscale service tier, or its original service tier. If the geo-secondary database is in an elastic pool before conversion, it is taken out of the pool and might need to be added back to a Hyperscale elastic pool separately after the conversion. The deployment of the feature is in progress and is expected to be completed in all Azure regions in a few weeks. In case you see error (Update to service objective '<SLO name>' with source DB geo-replicated is not supported for entity '<Database Name>') while converting primary to Hyperscale, wait for this new improvement to become available in your region. If you don’t want to use this preview capability yet, make sure to remove any geo-replication configuration before converting your databases to Hyperscale. Conclusion This update marks a significant step forward in the Hyperscale conversion process, offering simple steps, less downtime and keeping the geo-secondary available during the conversion process. We encourage you to try this new capability and provide your valuable feedback and help us refine this feature for general availability. You can contact us by commenting on this blog post and we’ll be happy to get back to you. Alternatively, you can also email us at sqlhsfeedback AT microsoft DOT com. We are eager to hear from you all!Azure Data Studio Retirement
We’re announcing the upcoming retirement of Azure Data Studio (ADS) on February 6, 2025, as we focus on delivering a modern, streamlined SQL development experience. ADS will remain supported until February 28, 2026, giving developers ample time to transition. This decision aligns with our commitment to simplifying SQL development by consolidating efforts on Visual Studio Code (VS Code) with the MSSQL extension, a powerful and versatile tool designed for modern developers. Why Retire Azure Data Studio? Azure Data Studio has been an essential tool for SQL developers, but evolving developer needs and the rise of more versatile platforms like VS Code have made it the right time to transition. Here’s why: Focus on innovation VS Code, widely adopted across the developer community, provides a robust platform for delivering advanced features like cutting-edge schema management and improved query execution. Streamlined tools Consolidating SQL development on VS Code eliminates duplication, reduces engineering maintenance overhead, and accelerates feature delivery, ensuring developers have access to the latest innovations. Why Transition to Visual Studio Code? VS Code is the #1 developer tool, trusted by millions worldwide. It is a modern, versatile platform that meets the evolving demands of SQL and application developers. By transitioning, you gain access to cutting-edge tools, seamless workflows, and an expansive ecosystem designed to enhance productivity and innovation. We’re committed to meeting developers where they are, providing a modern SQL development experience within VS Code. Here’s how: Modern development environment VS Code is a lightweight, extensible, and community-supported code editor trusted by millions of developers. It provides: Regular updates. An active extension marketplace. A seamless cross-platform experience for Windows, macOS, and Linux. Comprehensive SQL features With the MSSQL extension in VS Code, you can: Execute queries faster with filtering, sorting, and export options for JSON, Excel, and CSV. Manage schemas visually with Table Designer, Object Explorer, and support for keys, indexes, and constraints. Connect to SQL Server, Azure SQL (all offerings), and SQL database in Fabric using an improved Connection Dialog. Streamline development with scripting, object modifications, and a unified SQL experience. Optimize performance with an enhanced Query Results Pane and execution plans. Integrate with DevOps and CI/CD pipelines using SQL Database Projects. Stay tuned for upcoming features—we’re continuously building new experiences based on feedback from the community. Make sure to follow the MSSQL repository on GitHub to stay updated and contribute to the project! Streamlined workflow VS Code supports cloud-native development, real-time collaboration, and thousands of extensions to enhance your workflows. Transitioning to Visual Studio Code: What You Need to Know We understand that transitioning tools can raise concerns, but moving from Azure Data Studio (ADS) to Visual Studio Code (VS Code) with the MSSQL extension is designed to be straightforward and hassle-free. Here’s why you can feel confident about this transition: No Loss of Functionality If you use ADS to connect to Azure SQL databases, SQL Server, or SQL database in Fabric, you’ll find that the MSSQL extension supports these scenarios seamlessly. Your database projects, queries, and scripts created in ADS are fully compatible with VS Code and can be opened without additional migration steps. Familiar features, enhanced experience VS Code provides advanced tools like improved query execution, modern schema management, and CI/CD integration. Additionally, alternative tools and extensions are available to replace ADS capabilities like SQL Server Agent and Schema Compare. Cross-Platform and extensible Like ADS, VS Code runs on Windows, macOS, and Linux, ensuring a consistent experience across operating systems. Its extensibility allows you to adapt it to your workflow with thousands of extensions. If you have further questions or need detailed guidance, visit the ADS Retirement page. The page includes step-by-step instructions, recommended alternatives, and additional resources. Continued Support With the Azure Data Studio retirement, we’re committed to supporting you during this transition: Documentation: Find detailed guides, tutorials, and FAQs on the ADS Retirement page. Community Support: Engage with the active Visual Studio Code community for tips and solutions. You can also explore forums like Stack Overflow. GitHub Issues: If you encounter any issues, submit a request or report bugs on the MSSQL extension’s GitHub repository. Microsoft Support: For critical issues, reach out to Microsoft Support directly through your account. Transitioning to VS Code opens the door to a more modern and versatile SQL development experience. We encourage you to explore the new possibilities and start your journey today! Conclusion Azure Data Studio has served the SQL community well,but the Azure Data Studio retirement marks an opportunity to embrace the modern capabilities of Visual Studio Code. Transitioning now ensures you’re equipped with cutting-edge tools and a future-ready platform to enhance your SQL development experience. For a detailed guide on ADS retirement , visit aka.ms/ads-retirement. To get started with the MSSQL extension, check out the official documentation. We’re excited to see what you build with VS Code!Unlocking More Power with Flexible Memory in Azure SQL Managed Instance
As data workloads grow in complexity and scale, so does the need for more adaptable and performant database infrastructure. That’s why we’re excited to introduce a new capability in Azure SQL Managed Instance: Flexible Memory, now entering public preview. What Is Flexible Memory? Flexible Memory allows you to customize the memory-to-vCore ratio in your SQL Managed Instance, giving you the ability to fine-tune performance and cost based on your workload needs. This feature is part of the next-generation General Purpose tier, and it introduces a memory slider that lets you scale memory independently within defined limits. The memory slider is enabled only for premium series hardware. Why It Matters Traditionally, memory allocation in SQL Managed Instance was fixed per vCore. With Flexible Memory, you can now: Increase memory beyond the default allocation Optimize for memory-intensive workloads without overprovisioning compute Pay only for what you use — additional memory is billed per GB/hour This flexibility is especially valuable for scenarios like analytics, caching, or workloads with large buffer pool requirements. How It Works Memory scales based on the number of vCores and the selected hardware tier: Hardware Tier Memory per vCore (GB) Standard-series 5.1 Premium series 7–12 Premium series (memory-optimized) Up to 13.6 You can select from predefined memory ratios (e.g., 7, 8, 10, 12 GB per vCore) depending on your configuration. For example, a 10 vCore instance can be configured with 70 GB to 120 GB of memory. One of the most powerful aspects of the Flexible Memory feature is the ability to select from a range of memory-to-vCore ratios. These “click stops” allow you to tailor memory allocation precisely to your workload’s needs — whether you’re optimizing for performance, cost, or both. The table below outlines the available configurations for Premium Series hardware, showing how memory scales across 16 vCore sizes: vCores Available Ratios Total Memory Options (GB) 4 7, 8, 10, 12 28, 32, 40, 48 6 7, 8, 10, 12 42, 48, 60, 72 8 7, 8, 10, 12 56, 64, 80, 96 10 7, 8, 10, 12 70, 80, 100, 120 12 7, 8, 10, 12 84, 96, 120, 144 16 7, 8, 10, 12 112, 128, 160, 192 20 7, 8, 10, 12 140, 160, 200, 240 24 7, 8, 10, 12 168, 192, 240, 288 32 7, 8, 10, 12 224, 256, 320, 384 40 7, 8, 10, 12 280, 320, 400, 480 48 7, 8, 10 336, 384, 480 56 7, 8 392, 448 64 7 448 80 7 560 96 5.83 560 128 4.38 560 Pricing model Flexible Memory introduces a usage-based pricing model that ensures you only pay for the memory you actually consume beyond the default allocation. This model is designed to give you the flexibility to scale memory without overcommitting on compute resources - and without paying for unused capacity. How it works: Default memory is calculated based on the minimum memory-to-vCore ratio Billable memory is the difference between your configured memory and the default allocation. Billing is per GB/hour, so you’re charged only for the additional memory used over time. Let’s take an example of SQL Managed Instance running on premium series hardware with 4 vCores and 40GB of memory. Configuration Value vCores 4 Configured Memory 40 GB Default Memory (4 × 7 GB) 28 GB Billable Memory 12 GB Billing Unit Per GB/hour Charged For 12 GB of additional memory Important note: Additional memory is provided free of charge until September 1 st. Management Experience Changing memory behaves just like changing vCores: Seamless updates via Azure Portal or API Failover group guidance remains the same Upgrade secondary first Configurations between primary and secondary should match Adjusting the memory is fully online operation, with a short failover at the very end of it. The operation will go through the process of allocating the new compute with specified configuration, which takes approximately 60 minutes, with new faster management operations. API Support Flexible Memory is fully supported via API (the minimal API version that can be used is 2024-08-01) and Azure Portal. Here’s a sample API snippet to configure memory: { "properties": { "memorySizeInGB": 96 } } Portal support Notice: Changes in Azure portal are being rolled out. In the meantime, you can use API for trying out the feature. Summary The new Flexible Memory capability in Azure SQL Managed Instance empowers you to scale memory independently of compute, offering greater control over performance and cost. With customizable memory-to-vCore ratios, a transparent pricing model, and seamless integration into existing management workflows, this feature is ideal for memory-intensive workloads and dynamic scaling scenarios. Whether you're optimizing for analytics, caching, or simply want more headroom without overprovisioning vCores, Flexible Memory gives you the tools to do it - efficiently and affordably. Next Steps Review the Documentation: Explore detailed configuration options, supported tiers, and API usage. Additional memory Management operations overview Management operations duration Test Your Workloads: Use the memory slider in the Azure Portal or API to experiment with different configurations.Faster Management Operations in Azure SQL Managed Instance
We are excited to introduce a faster management operations experience that offers greater elasticity for Azure SQL Managed Instance, improving the speed and efficiency of managing your resources. The new experience ensures that your database infrastructure can scale and adapt swiftly to meet the dynamic demands of your business. What are faster management operations? Offering an elastic and responsive cloud service isn’t just about ensuring a smooth sailing customer experience. It’s about providing users with the highest degree of flexibility, allowing them to have as much governance over their resources as possible. Giving users a prompt way to manage their resources allows for greater efficiency and adaptability to dynamic workflows. Instant availability and acquisition of resources is what makes all the difference. Faster management operations bring enormous improvements, making it easier and faster to create and update your instances, while giving you the flexibility to closely align your database configuration with your workload needs. By improving underlying processes, like creating the virtual cluster and allocating resources, we managed to significantly cut down the time it takes to deploy or update your instances. The following is an outline of the improvement that faster management operations brings: Previous experience Faster management operations Deployment 30 minutes (limited only to default configurations) 4h for non-default configurations 30 minutes for any configuration Scaling 4h for any kind of scale operation 60 minutes for any kind of scale operation This means you can adapt quickly to fluctuating demands, keep your systems running smoothly, and make the most of your resources—all while reducing the effort involved in managing your infrastructure. Note: Faster management operations do not apply to zone redundant (ZR) instances. Deployment: Spin up instances in less than 30 Minutes Deploying Azure SQL Managed Instance is now faster and easier than ever. With the enhanced provisioning process, you can have your instance up and running in less than 30 minutes, no matter the configuration of the instance you are provisioning or your existing network setup. This kind of rapid scalability is essential when preparing for predictable, high-demand events—like Black Friday or major product launches. By leveraging horizontal scaling, you can proactively provision additional instances ahead of time to handle the anticipated surge in traffic. This ensures your services remain stable and responsive under pressure, avoiding performance bottlenecks or downtime. With the right planning, you can maintain a seamless user experience even during peak loads, keeping operations smooth and customer satisfaction high. It's also highly beneficial for teams working on testing and development. For instance, when launching new features or making system updates, having the ability to rapidly set up environments for testing and development allows teams to experiment without the usual delays. They can create and tear down instances as needed, run simulations, and automate tasks more efficiently, reducing operational overhead. This reduces the time spent on setup and allows teams to focus on actual development or testing, leading to faster delivery of products and improvements while also freeing up resources. Updates: Streamlined Modifications in less than 60 Minutes This feature offers you the flexibility to easily update your SQL Managed Instance resources, whether you're scaling compute power, adjusting storage, or changing service tiers. These updates are now executed quickly—typically in under 60 minutes—so you can keep your systems running smoothly without long disruptions. For example, consider a scenario where you have an instance that’s optimized to handle around 70-80% of its capacity during regular business hours. This setup ensures you're using resources efficiently without over-provisioning. However, if your system unexpectedly experiences a spike in demand—such as a sudden influx of users during a busy period or a promotion—you can quickly scale up your instance to handle the extra load. Once traffic returns to normal, you can scale back down, ensuring that you’re only using and paying for the resources you need at any given time. This approach tightly aligns your capacity with your workload, helping to avoid unnecessary costs while ensuring your systems remain responsive. These improvements make it simple to match your database setup to your business needs. Whether you’re preparing for a busy product launch or anticipating a seasonal rush, scaling resources up or down in real time allows you to maintain optimal performance without breaking the bank. This ability to adjust resources quickly and efficiently keeps your systems cost-effective and ready for whatever challenges come your way. Notice: Operations within the Business Critical service tier require data seeding due to its reliance on local storage architecture. As a result, tasks such as compute scaling or storage modifications may take longer to complete. This extension is primarily caused by the seeding process, which increases in duration proportionally with the size of the database. Real-World Impact: Customer Benefits The enhanced Faster management operations capabilities for Azure SQL Managed Instance translate into tangible advantages for businesses, enabling them to scale and adapt swiftly to meet dynamic demands. Key Benefits: Increased Elasticity: Rapid provisioning and updates allow businesses to scale resources in response to real-time demands, facilitating quick adaptation to changing workloads. Cost Optimization: Efficient operations reduce the need for over-provisioning, optimizing resource utilization and enabling businesses to align costs with actual usage. Enhanced User Experience: Faster deployment and update times minimize disruptions, time and staff occupation, leading to improved service availability and seamless user experience. Improved Business Continuity: Rapid scaling capabilities ensure that businesses can maintain performance levels during peak periods, reducing the risk of service degradation or throttling. Who will benefit from this? This enhancement benefits all SQL Managed Instance (SQL MI) customers, especially: IaaC Users (e.g., Terraform, Bicep): Automate and streamline deployment processes with faster management operations, achieving greater efficiency and consistency. Cost Optimization Seekers: Quickly adjust resource allocation to match workload, ensuring cost-effectiveness by paying only for what is needed. Elasticity Users for Usage Peaks: Rapidly scale resources to handle fluctuating workloads, maintaining system responsiveness during peak periods. CI/CD Process Users: Facilitate faster development cycles and efficient testing with reduced time for resource provisioning and updates. Here is an example of a cost-saving benefit for cost optimization seekers: A 6 vCore instance is necessary to manage your workload during weekdays (Monday to Friday). However, the workload decreases on the weekend. Therefore, it is logical to scale down the instance on Friday and then scale it back up on Monday. You would scale the instance down to the minimal acceptable capacity that corresponds to the reduced workload. Next gen General Purpose service tier, Gen5 Hardware instances with 6 vCores and 4 vCores, along with 2TB of storage are under consideration. Comparison Table Scenario vCore configuration Time billed Monthly cost No scaling (Stay at 6 vCores all week) 6 vCores 24 hours/day, 30 days/month $1,350 Scaling down to 4 vCores (weekend) 6 vCores (Mon–Fri) 24 hours/day, 5 days/week $900 4 vCores (Fri–Mon) 24 hours/day, 2 days/week $300 Monthly savings — — $150 Note: The prices are approximate and for demonstration purpose only. Availability Faster management operations feature for Azure SQL Managed Instance is now in General Availability. This means that the enhanced provisioning and updating capabilities are fully integrated and available on all service tiers for all customers. The feature is seamlessly incorporated into all management operations, requiring no additional configuration in the Azure portal and incurring no extra charges. It does not apply to Zone Redundant Instances. Summary The Faster management operations feature in Azure SQL Managed Instance significantly enhances the speed and efficiency of managing database resources. It allows for rapid deployment of instances in under 30 minutes and updates in less than 60 minutes, optimizing resource utilization and reducing operational overhead. This capability ensures businesses can swiftly adapt to changing demands, maintain high availability, and improve overall performance and cost efficiency. Useful links: What is Azure SQL Managed Instance? - Azure SQL Managed Instance | Microsoft Learn Quickstart: Create Azure SQL Managed Instance - Azure SQL Managed Instance | Microsoft Learn Management operations overview Management operations durationIntroducing Azure SQL Managed Instance Next-gen GP
The next generation of the general purpose service tier for Azure SQL Managed Instance is a major upgrade that will considerably improve the storage performance of your instances while keeping the same price as current general purpose tier. Key improvements in the next generation of general purpose storage include support for 32 TB of storage, support for 500 DBs, lower storage latency, improved storage performance, and the ability to configure the amount of IOPS (I/O operations per second).Stream data changes from Azure SQL Managed Instance and Azure SQL Database – private preview of CES
[Edit May 19th, 2025: CES is available in public preview of SQL Server 2025 CTP 2.0 - https://learn.microsoft.com/en-us/sql/relational-databases/track-changes/change-event-streaming/overview?view=sql-server-ver17] We’re excited to share that Change Event Streaming (CES) - the capability to stream data changes directly from your SQL into Azure Event Hubs - is now also available in private preview for Azure SQL Managed Instance. CES enables implementing near real-time data integration and event-driven architectures with minimal overhead, helping you keep systems in sync, power real-time analytics, and track changes as they happen. Whether you’re working with Azure SQL Managed Instance or Azure SQL Database, you can now join the private preview and: Try out the new functionality early. Collaborate with the product team. Share feedback that helps shape the final product. To apply for the private preview today, send an email to sqlcesfeedback [at] microsoft [dot] com or fill in the form at https://aka.ms/sql-ces-signup. More on CES available in the previous blog post. More useful resources: Free Azure SQL Database. Free Azure SQL Managed Instance. Azure SQL – Year 2024 in review. Azure SQL YouTube channel.Azure SQL Managed Instance pools: General Availability
We are happy to announce new features and General Availability for instance pools. Instance pools are a deployment option in Azure SQL Managed instance service to provision small, cost-effective 2-vCore instances. This way, small instances can cost 50% less compared to non-pooled instances, making it an attractive PaaS target when migrating small on-premises servers or modernizing SQL VMs.
