Home
%3CLINGO-SUB%20id%3D%22lingo-sub-978563%22%20slang%3D%22fr-FR%22%3ERe%3A%20New%20memory%20and%20compute%20optimized%20hardware%20options%20in%20Azure%20SQL%20Database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-978563%22%20slang%3D%22fr-FR%22%3E%3CP%3ESounds%20great%20and%20very%20interseting!%3C%2FP%3E%3CP%3EIs%20there%20any%20limitation%2Frestrication%20regarding%20switching%20an%20elastic%20pool%20from%20Gen5%20to%20Fsv2%3F%3C%2FP%3E%3CP%3EIt%20seems%20when%20we%20want%20to%20proceed%20to%20the%20upgrade%2C%20it%20selectby%20default%2072%20vcores.%20Is%20it%20a%20bug%20or%20this%20feature%20necesseraly%20requires%20to%20buy%2072%20vcore%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20very%20much%20for%20your%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-978786%22%20slang%3D%22en-US%22%3ERe%3A%20New%20memory%20and%20compute%20optimized%20hardware%20options%20in%20Azure%20SQL%20Database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-978786%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20no%20restrictions%20in%20moving%20from%20Gen5%20to%20Fsv2%20other%20than%20restrictions%20associated%20with%20the%20General%20Purpose%20service%20tier.%26nbsp%3B%2072%20vcores%20is%20the%20only%20compute%20size%20currently%20available%20for%20Fsv2%20although%20smaller%20sizes%20are%20under%20consideration%20in%20the%20future.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-978808%22%20slang%3D%22en-US%22%3ERe%3A%20New%20memory%20and%20compute%20optimized%20hardware%20options%20in%20Azure%20SQL%20Database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-978808%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20your%20prompt%20answer.%3C%2FP%3E%3CP%3EOk%20it%20is%20clear%2C%2072vcore%20was%20not%20specified%20to%20be%20for%20the%20moment%20the%20only%20compute%20size.%3C%2FP%3E%3CP%3EWe%20will%20follow%20closely%20once%20%22smaller%20size%22%20will%20be%20considered.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-988928%22%20slang%3D%22en-US%22%3ERe%3A%20New%20memory%20and%20compute%20optimized%20hardware%20options%20in%20Azure%20SQL%20Database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-988928%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20idea%20of%20when%20we%20will%20be%20able%20to%20provision%20an%20Azure%20SQL%20Elastic%20Pool%20on%20M%20Series%20with%208%20vCore%20Business%20Critical%3F%20We%20really%20could%20benefit%20from%20the%20new%20hardware%20but%20only%20need%208%2C%2016%2C%20or%2024vcore%20-%20128%20is%20simply%20just%20way%20too%20much.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-989061%22%20slang%3D%22en-US%22%3ERe%3A%20New%20memory%20and%20compute%20optimized%20hardware%20options%20in%20Azure%20SQL%20Database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-989061%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20feedback.%26nbsp%3B%20Providing%20smaller%20M-series%20compute%20sizes%20in%20the%20future%20is%20under%20consideration.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-966830%22%20slang%3D%22en-US%22%3ENew%20memory%20and%20compute%20optimized%20hardware%20options%20in%20Azure%20SQL%20Database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-966830%22%20slang%3D%22en-US%22%3E%3CP%3ENow%20in%20preview%2C%20M-series%20and%20Fsv2-series%20are%20new%20hardware%20generations%20in%20Azure%20SQL%20Database%20specialized%20for%20workloads%20requiring%20very%20high%20compute%20or%20memory%20scale%2C%20or%20very%20fast%20CPU%20speed.%26nbsp%3B%20Gen5%20in%20SQL%20Database%20continues%20to%20provide%20a%20balanced%20compute%20and%20memory%20option%20that%20is%20well-suited%20for%20typical%20workloads.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20size%3D%225%22%3EM-series%3A%20memory%20optimized%20hardware%3C%2FFONT%3E%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EM-series%20(preview)%20is%20a%20new%20memory%20optimized%20hardware%20option%20in%20SQL%20Database%20for%20workloads%20demanding%20more%20memory%20and%20higher%20compute%20limits%20than%20provided%20by%20Gen5.%26nbsp%3B%20M-series%20provides%2029%20GB%20per%20vcore%20and%20128%20vcores%20which%20increases%20the%20previous%20memory%20limit%20in%20SQL%20Database%20by%208x%20to%20nearly%204%20TB.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EFsv2-series%3A%20compute%20optimized%20hardware%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EFsv2-series%20(preview)%20is%20a%20new%20compute%20optimized%20hardware%20option%20in%20SQL%20Database%20delivering%20low%20CPU%20latency%20and%20high%20clock%20speed%20for%20the%20most%20CPU%20demanding%20workloads.%26nbsp%3B%20Depending%20on%20the%20workload%2C%20Fsv2-series%20can%20deliver%20more%20CPU%20performance%20per%20vcore%20than%20Gen5.%26nbsp%3B%20The%2072%20vcore%20size%20can%20also%20provide%20more%20CPU%20performance%20for%20less%20cost%20than%2080%20vcores%20on%20Gen5.%26nbsp%3B%20Note%20that%20Fsv2%20provides%20less%20memory%20and%20tempdb%20per%20vcore%20than%20other%20hardware%20so%20workloads%20sensitive%20to%20those%20limits%20may%20want%20to%20consider%20Gen5%20or%20M-series%20instead.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3ELearn%20more%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ELearn%20more%20about%20M-series%20and%20Fsv2-series%20%3CA%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3Flinkid%3D2110517%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehardware%20generations%3C%2FA%3E%20in%20Azure%20SQL%20Database.%3C%2FLI%3E%0A%3CLI%3ELearn%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fpricing%2Fdetails%2Fsql-database%2Fsingle%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20SQL%20Database%20pricing%3C%2FA%3E%20for%20M-series%20and%20Fsv2-series.%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-966830%22%20slang%3D%22en-US%22%3E%3CP%3EN%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23333333%3B%20cursor%3A%20text%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSPAN%20style%3D%22background-color%3A%20%23ffffff%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20cursor%3A%20text%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3Eow%20in%20preview%3C%2FSPAN%3E%2C%20M-series%20and%20Fsv2-series%20are%20new%20hardware%20generations%20in%20SQL%20Database%20specialized%20for%20very%20high%20performance%20workloads%3C%2FSPAN%3E.%3C%2FP%3E%3C%2FLINGO-TEASER%3E
Microsoft

Now in preview, M-series and Fsv2-series are new hardware generations in Azure SQL Database specialized for workloads requiring very high compute or memory scale, or very fast CPU speed.  Gen5 in SQL Database continues to provide a balanced compute and memory option that is well-suited for typical workloads.

 

M-series: memory optimized hardware

M-series (preview) is a new memory optimized hardware option in SQL Database for workloads demanding more memory and higher compute limits than provided by Gen5.  M-series provides 29 GB per vcore and 128 vcores which increases the previous memory limit in SQL Database by 8x to nearly 4 TB.

 

Fsv2-series: compute optimized hardware

Fsv2-series (preview) is a new compute optimized hardware option in SQL Database delivering low CPU latency and high clock speed for the most CPU demanding workloads.  Depending on the workload, Fsv2-series can deliver more CPU performance per vcore than Gen5.  The 72 vcore size can also provide more CPU performance for less cost than 80 vcores on Gen5.  Note that Fsv2 provides less memory and tempdb per vcore than other hardware so workloads sensitive to those limits may want to consider Gen5 or M-series instead.

 

Learn more

5 Comments
Occasional Visitor

Sounds great and very interseting!

Is there any limitation/restrication regarding switching an elastic pool from Gen5 to Fsv2 ?

It seems when we want to proceed to the upgrade, it select by default 72 vcores. Is it a bug or this feature necesseraly requires to buy 72 vcore?

 

Thank you very much for your help.

Microsoft

There are no restrictions in moving from Gen5 to Fsv2 other than restrictions associated with the General Purpose service tier.  72 vcores is the only compute size currently available for Fsv2 although smaller sizes are under consideration in the future.

Occasional Visitor

Thank you for your prompt answer.

Ok it is clear, 72vcore was not specified to be for the moment the only compute size.

We will follow closely once "smaller size" will be considered.

 

New Contributor

Any idea of when we will be able to provision an Azure SQL Elastic Pool on M Series with 8 vCore Business Critical? We really could benefit from the new hardware but only need 8, 16, or 24vcore - 128 is simply just way too much. 

Microsoft

Thanks for the feedback.  Providing smaller M-series compute sizes in the future is under consideration.