Azure SQL Managed Instance Business Critical 16 TB is now in limited public preview

Published Nov 02 2021 05:57 AM 2,051 Views
Microsoft

Storage limit of 16TB is now in limited public preview for SQL Managed Instance (SQL MI) Business Critical (BC) tier, along with increased storage to vCore ratios.

Note: A few months ago, we launched a preview for SQL MI General Purpose (GP) 16 TB. From today, the 16 TB storage is in general availability for SQL MI GP!

 

What is new?

SQL Managed Instance Business Critical 16 TB scale: For many database workloads with significant data volume, but utmost storage latency and availability requirements, the previous limit for SQL MI BC storage size of 4 TB has been a challenge. We are happy to announce that the storage limit for BC is quadrupled and you can create or upgrade your BC Instances to host up to 16 TB of data.

Increased storage to vCore ratios: You might ask what about other prerequisites; for example, to use 2 TB of storage, one must have had a BC instance with at least 24 vCores. Do not worry, we also improved storage to vCore ratios on the way to 16 TB. Now, to use 2 TB of storage, one must have a BC instance with only 16 vCores. This will save you 8 vCores expense or, if you have a failover group, this means 16 vCores of saving! Check out the “Are there any requirements?” section below for the full list of the new storage to vCore ratios. 

 

What is a limited public preview and how can I sign up for it?

In this sense, limited preview stands for the public preview that is available in a limited number of regions. In these regions, SQL MI BC 16 TB is in public preview meaning that there is no need to sign up.

 

What regions are supported?

To be eligible for 16 TB of storage, SQL MI Business Critical instance must be in one of the regions where the preview is available. The list of the supported regions will change as we roll out this improvement incrementally across the globe and you can check on the latest status here.

 

Are there any requirements?

Yes. To be able to choose a specific combination of storage size and vCore count, your SQL MI BC instance must be running on a particular hardware generation. For instance, to have 16 TB of storage in SQL MI BC, you need to configure the compute as: Premium series – memory optimized hardware generation and 64 vCores. See Figure 1.

NevenaNikolic_0-1635783272392.png

Figure 1 - Azure Portal experience when configuring Compute + Storage

 

To understand this requirement better, we should introduce our new hardware generations first.

 

New hardware generations

The new premium-series hardware is based on Intel® Ice Lake processors which provide better compute and memory performance as well as improved IO and network experience over the standard-series (Gen5) hardware offering. A new memory optimized option within the premium-series provides even more memory per vCore and is thereby optimal for the most memory-intensive workloads. See Table 1.

Hardware Generation

Hardware

Max memory per vCore

Standard Series (Gen5)

Intel® Broadwell , Intel® Skylake, Intel® Cascade Lake

5.1 GB RAM/vCore

Premium Series

Intel® Ice Lake

7 GB RAM/vCore

Premium Series – Memory Optimized

Intel® Ice Lake

13.6 GB RAM/vCore

Table 1 - Key characteristics for  new SQL MI hardware generations

 

For more details on the new hardware generations and their characteristics, see the Announcing the new premium-series hardware for SQL Managed Instance blog.

Increased storage to vCore ratios - more storage for less vCores!

Previously, the maximum storage size for SQL MI BC was 4 TB, which was available for every BC instance that had at least 32 vCores (Table 2, column SQL MI BC - BEFORE). Now, with BC 16 TB in preview, this experience changes according to the mapping shown in Table 2, column SQL MI BC – NOW.

Feature

SQL MI BC - BEFORE

SQL MI BC – NOW (new in orange)

Max instance storage size (reserved)

Gen4: 1 TB
Gen5:
- 1 TB for 4, 8, 16 vCores
- 2 TB for 24 vCores
- 4 TB for 32, 40, 64, 80 vCores

Standard-Series (Gen5)
- 1 TB for 4, 8, 16 vCores
- 2 TB for 24 vCores
- 4 TB for 32, 40, 64, 80 vCores
Premium­-Series:

- 1 TB for 4, 8 vCores
- 2 TB for 16, 24 vCores
- 4 TB for 32 vCores

- 5.5 TB for 40, 64, 80 vCores
Premium-Series - Memory Optimized:

- 1 TB for 4, 8 vCores
- 2 TB for 16, 24 vCores
- 4 TB for 32 vCores

- 5.5 TB for 40 vCores

- 16 TB for 64 vCores

Table 2 - Storage to vCore ratios in SQL MI BC 

 

For more details on other limitations, see SQL Managed Instance resource limits.

 

Summary

In this article, we've discussed the latest scale and performance improvements in SQL Managed Instance Business Critical: SQL Managed Instance Business Critical with 16 TB storage and more favorable storage size limits per vCore count. Thank you for reading and enjoy using SQL Managed Instance with increased storage capacity and much better performance.

%3CLINGO-SUB%20id%3D%22lingo-sub-2909332%22%20slang%3D%22en-US%22%3EAzure%20SQL%20Managed%20Instance%20Business%20Critical%2016%20TB%20is%20now%20in%20limited%20public%20preview%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2909332%22%20slang%3D%22en-US%22%3E%3CP%3EStorage%20limit%20of%2016TB%20is%20now%20in%20limited%20public%20preview%20for%20SQL%20Managed%20Instance%20(SQL%20MI)%20Business%20Critical%20(BC)%20tier%2C%20along%20with%20increased%20storage%20to%20vCore%20ratios.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3A%20A%20few%20months%20ago%2C%20we%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-sql%2Fincreased-storage-limit-to-16-tb-for-sql-managed-instance%2Fba-p%2F2421443%22%20target%3D%22_blank%22%3Elaunched%20a%20preview%3C%2FA%3E%26nbsp%3Bfor%20SQL%20MI%20General%20Purpose%20(GP)%2016%20TB%3CSPAN%3E.%3C%2FSPAN%3E%26nbsp%3BFrom%20today%2C%20the%2016%20TB%20storage%20is%20in%20general%20availability%20for%20SQL%20MI%20GP!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-1497292961%22%20id%3D%22toc-hId-1498043414%22%3EWhat%20is%20new%3F%3C%2FH1%3E%0A%3CP%3E%3CSTRONG%3E%3CU%3ESQL%20Managed%20Instance%20Business%20Critical%2016%20TB%20scale%3C%2FU%3E%3C%2FSTRONG%3E%3A%20For%20many%20database%20workloads%20with%20significant%20data%20volume%2C%20but%20utmost%20storage%20latency%20and%20availability%20requirements%2C%20the%20previous%20limit%20for%20SQL%20MI%20BC%20storage%20size%20of%204%20TB%20has%20been%20a%20challenge.%20We%20are%20happy%20to%20announce%20that%20the%20storage%20limit%20for%20BC%20is%20quadrupled%26nbsp%3B%3CSPAN%3Eand%3C%2FSPAN%3E%20you%20can%20create%20or%20upgrade%20your%20BC%20Instances%20to%20host%20up%20to%2016%20TB%20of%20data.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CU%3EIncreased%20storage%20to%20vCore%20ratios%3C%2FU%3E%3C%2FSTRONG%3E%3A%20You%20might%20ask%20what%20about%20other%20prerequisites%3B%20for%20example%2C%20to%20use%202%20TB%20of%20storage%2C%20one%20must%20have%20had%20a%20BC%20instance%20with%20at%20least%2024%20vCores.%20Do%20not%20worry%2C%20we%20also%20improved%20storage%20to%20vCore%20ratios%20on%20the%20way%20to%2016%20TB.%20Now%2C%20to%20use%202%20TB%20of%20storage%2C%20one%20must%20have%20a%20BC%20instance%20with%20only%2016%20vCores.%20This%20will%20save%20you%208%20vCores%20expense%20or%2C%20if%20you%20have%20a%20failover%20group%2C%20this%20means%2016%20vCores%20of%20saving!%20Check%20out%20the%20%E2%80%9CAre%20there%20any%20requirements%3F%E2%80%9D%20section%20below%20for%20the%20full%20list%20of%20the%20new%20storage%20to%20vCore%20ratios.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId--310161502%22%20id%3D%22toc-hId--309411049%22%3EWhat%20is%20a%20limited%20public%20preview%20and%20how%20can%20I%20sign%20up%20for%20it%3F%3C%2FH1%3E%0A%3CP%3EIn%20this%20sense%2C%20limited%20preview%20stands%20for%20the%20public%20preview%20that%20is%20available%20in%20a%20limited%20number%20of%20regions.%20In%20these%20regions%2C%20SQL%20MI%20BC%2016%20TB%20is%20in%20public%20preview%20meaning%20that%20there%20is%20%3CSTRONG%3Eno%20need%20to%20sign%20up%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId--2117615965%22%20id%3D%22toc-hId--2116865512%22%3EWhat%20regions%20are%20supported%3F%3C%2FH1%3E%0A%3CP%3ETo%20be%20eligible%20for%2016%20TB%20of%20storage%2C%20SQL%20MI%20Business%20Critical%20instance%20must%20be%20in%20one%20of%20the%20regions%20where%20the%20preview%20is%20available.%20The%20list%20of%20the%20supported%20regions%20will%20change%20as%20we%20roll%20out%20this%20improvement%20incrementally%20across%20the%20globe%20and%20you%20can%20check%20on%20the%20latest%20status%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-sql%2Fmanaged-instance%2Fresource-limits%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-369896868%22%20id%3D%22toc-hId-370647321%22%3EAre%20there%20any%20requirements%3F%3C%2FH1%3E%0A%3CP%3EYes.%20To%20be%20able%20to%20choose%20a%20specific%20combination%20of%20storage%20size%20and%20vCore%20count%2C%20your%20SQL%20MI%20BC%20instance%20must%20be%20running%20on%20a%20particular%20hardware%20generation.%20For%20instance%2C%20to%20have%2016%20TB%20of%20storage%20in%20SQL%20MI%20BC%2C%20you%20need%20to%20configure%20the%20compute%20as%3A%20%3CSTRONG%3EPremium%20series%20%E2%80%93%20memory%20optimized%3C%2FSTRONG%3E%20hardware%20generation%20and%2064%20vCores.%20See%20Figure%201.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22NevenaNikolic_0-1635783272392.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F322257i9BBC84F8CB4F0A50%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22NevenaNikolic_0-1635783272392.png%22%20alt%3D%22NevenaNikolic_0-1635783272392.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EFigure%201%20-%20Azure%20Portal%20experience%20when%20configuring%20Compute%20%2B%20Storage%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20understand%20this%20requirement%20better%2C%20we%20should%20introduce%20our%20new%20hardware%20generations%20first.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1060458342%22%20id%3D%22toc-hId-1061208795%22%3ENew%20hardware%20generations%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3EThe%20new%20premium-series%20hardware%20is%20based%20on%20Intel%C2%AE%26nbsp%3BIce%20Lake%20processors%20which%20provide%26nbsp%3Bbetter%20compute%20and%20memory%20performance%20as%20well%20as%20improved%20IO%20and%20network%20experience%20over%20the%20standard-series%26nbsp%3B(Gen5%3C%2FSPAN%3E%3CSPAN%3E)%26nbsp%3Bhardware%20offering.%20A%20new%20memory%20optimized%26nbsp%3Boption%26nbsp%3Bwithin%20the%20premium-series%20provides%20even%20more%20memory%20per%26nbsp%3BvCore%26nbsp%3Band%20is%20thereby%20optimal%20for%20the%20most%20memory-intensive%26nbsp%3Bworkloads.%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3BSee%20Table%201.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CTABLE%20width%3D%22923px%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22306.328px%22%3E%3CP%3E%3CSPAN%3E%3CSTRONG%3EHardware%20Generation%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22397.422px%22%3E%3CP%3E%3CSPAN%3E%3CSTRONG%3EHardware%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22218.25px%22%3E%3CP%3E%3CSPAN%3E%3CSTRONG%3EMax%20memory%20per%20vCore%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22306.328px%22%3E%3CP%3E%3CSPAN%3EStandard%20Series%20(Gen5)%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22397.422px%22%3E%3CP%3E%3CSPAN%3EIntel%C2%AE%20Broadwell%20%2C%20Intel%C2%AE%20Skylake%2C%20Intel%C2%AE%20Cascade%20Lake%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22218.25px%22%3E%3CP%3E%3CSPAN%3E5.1%20GB%20RAM%2FvCore%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22306.328px%22%3E%3CP%3E%3CSPAN%3EPremium%20Series%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22397.422px%22%3E%3CP%3E%3CSPAN%3EIntel%3C%2FSPAN%3E%C2%AE%3CSPAN%3E%20Ice%20Lake%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22218.25px%22%3E%3CP%3E%3CSPAN%3E7%20GB%20RAM%2FvCore%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22306.328px%22%3E%3CP%3E%3CSPAN%3EPremium%20Series%20%E2%80%93%20Memory%20Optimized%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22397.422px%22%3E%3CP%3E%3CSPAN%3EIntel%3C%2FSPAN%3E%C2%AE%3CSPAN%3E%20Ice%20Lake%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22218.25px%22%3E%3CP%3E%3CSPAN%3E13.6%20GB%20RAM%2FvCore%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%3CEM%3ETable%201%20-%20Key%20characteristics%20for%26nbsp%3B%20new%20SQL%20MI%20hardware%20generations%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EFor%20more%20details%20on%20the%20new%20hardware%20generations%20and%20their%20characteristics%2C%20see%20the%26nbsp%3B%3C%2FSPAN%3E%3CA%20title%3D%22https%3A%2F%2Faka.ms%2Fsqlmi-ignite2021-newhwblog%22%20href%3D%22https%3A%2F%2Faka.ms%2Fsqlmi-ignite2021-newhwblog%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%22%3EAnnouncing%20the%20new%20premium-series%20hardware%20for%20SQL%20Managed%20Instance%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Eblog.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CLI-WRAPPER%3E%20%3C%2FLI-WRAPPER%3E%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--746996121%22%20id%3D%22toc-hId--746245668%22%3EIncreased%20storage%20to%20vCore%20ratios%20-%20more%20storage%20for%20less%20vCores!%3C%2FH2%3E%0A%3CP%3EPreviously%2C%20the%20maximum%20storage%20size%20for%20SQL%20MI%20BC%20was%204%20TB%2C%20which%20was%20available%20for%20every%20BC%20instance%20that%20had%20at%20least%2032%20vCores%20(Table%202%2C%20column%20SQL%20MI%20BC%20-%20BEFORE).%20Now%2C%20with%20BC%2016%20TB%20in%20preview%2C%20this%20experience%20changes%20according%20to%20the%20mapping%20shown%20in%20Table%202%2C%20column%20SQL%20MI%20BC%20%E2%80%93%20NOW.%3C%2FP%3E%0A%3CTABLE%20width%3D%22642%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22132%22%3E%3CP%3E%3CSTRONG%3EFeature%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22240%22%3E%3CP%3E%3CSTRONG%3ESQL%20MI%20BC%20-%20BEFORE%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22269%22%3E%3CP%3E%3CSTRONG%3ESQL%20MI%20BC%20%E2%80%93%20NOW%20(new%20in%20%3CFONT%20color%3D%22%23FF6600%22%3Eorange%3C%2FFONT%3E)%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22132%22%20class%3D%22lia-align-left%22%3E%3CP%3EMax%20instance%20storage%20size%20(reserved)%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22240%22%20class%3D%22lia-align-left%22%3E%3CP%3EGen4%3A%201%20TB%3CBR%20%2F%3EGen5%3A%3CBR%20%2F%3E-%201%20TB%20for%204%2C%208%2C%2016%20vCores%3CBR%20%2F%3E-%202%20TB%20for%2024%20vCores%3CBR%20%2F%3E-%204%20TB%20for%2032%2C%2040%2C%2064%2C%2080%20vCores%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22269%22%3E%3CP%3E%3CSTRONG%3EStandard-Series%20(Gen5)%3C%2FSTRONG%3E%3A%26nbsp%3B%3CBR%20%2F%3E-%26nbsp%3B1%20TB%20for%204%2C%208%2C%2016%20vCores%3CBR%20%2F%3E-%202%20TB%20for%2024%20vCores%3CBR%20%2F%3E-%204%20TB%20for%2032%2C%2040%2C%2064%2C%2080%20vCores%3CBR%20%2F%3E%3CSTRONG%3EPremium%C2%AD-Series%3C%2FSTRONG%3E%3A%3C%2FP%3E%0A%3CP%3E-%26nbsp%3B1%20TB%20for%204%2C%208%20vCores%3CBR%20%2F%3E-%20%3CFONT%20color%3D%22%23FF6600%22%3E2%20TB%20for%2016%3C%2FFONT%3E%2C%2024%20vCores%3CBR%20%2F%3E-%204%20TB%20for%2032%20vCores%3C%2FP%3E%0A%3CP%3E-%20%3CFONT%20color%3D%22%23FF6600%22%3E5.5%20TB%20for%2040%2C%2064%2C%2080%20vCores%3C%2FFONT%3E%3CBR%20%2F%3E%3CSTRONG%3EPremium-Series%20-%20Memory%20Optimized%3C%2FSTRONG%3E%3A%3C%2FP%3E%0A%3CP%3E-%26nbsp%3B1%20TB%20for%204%2C%208%20vCores%3CBR%20%2F%3E-%3CFONT%20color%3D%22%23FF6600%22%3E%202%20TB%20for%2016%3C%2FFONT%3E%2C%2024%20vCores%3CBR%20%2F%3E-%204%20TB%20for%2032%20vCores%3C%2FP%3E%0A%3CP%3E-%3CFONT%20color%3D%22%23FF6600%22%3E%205.5%20TB%20for%2040%20vCores%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E-%20%3CFONT%20color%3D%22%23FF6600%22%3E16%20TB%20for%2064%20vCores%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%3CEM%3ETable%202%20-%20Storage%20to%20vCore%20ratios%20in%20SQL%20MI%20BC%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20more%20details%20on%20other%20limitations%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-sql%2Fmanaged-instance%2Fresource-limits%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ESQL%20Managed%20Instance%20resource%20limits%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId--757499225%22%20id%3D%22toc-hId--756748772%22%3ESummary%3C%2FH1%3E%0A%3CP%3EIn%20this%20article%2C%20we've%20discussed%20the%20latest%20scale%20and%20performance%20improvements%20in%20SQL%20Managed%20Instance%20Business%20Critical%3A%20SQL%20Managed%20Instance%20Business%20Critical%20with%2016%20TB%20storage%20and%20more%20favorable%20storage%20size%20limits%20per%20vCore%20count.%20Thank%20you%20for%20reading%20and%20enjoy%20using%20SQL%20Managed%20Instance%20with%20increased%20storage%20capacity%20and%20much%20better%20performance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2909332%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22bc16.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F322276i16AF83345B1F9829%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22bc16.PNG%22%20alt%3D%22bc16.PNG%22%20%2F%3E%3C%2FSPAN%3EStorage%20limit%20of%2016TB%20for%20SQL%20Managed%20Instance%20Business%20Critical%20is%20out%20there!%26nbsp%3BEnjoy%20improved%20scale%20and%20performance%2C%20along%20with%20increased%20storage%20per%20vCore%20count%20in%20SQL%20MI%20BC!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2909332%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20SQL%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20SQL%20Managed%20Instance%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Co-Authors
Version history
Last update:
‎Nov 02 2021 08:11 AM
Updated by: