Azure SQL Hyperscale Deep Dive - NOT Just for Massive Databases!

[@NTFAQGuy]

Hey everyone, time to understand how Hyperscale works and where we can use it! Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc. 👂 Translate the captions to your native language via the auto-translate feature in settings! kzbin.info/www/bejne/rGbFZmZjhcx4o6s for a demo of using this feature. Thanks for watching! 🤙

[@ThorstenSauter]

Thanks for the explainer John! I never have looked at it for smaller workloads either. Fun fact, I followed your recommendation to check the documentation and the maximum storage actually goes up to 128TB and the 100TB is the maximum for elastic pool.

[@djpeter1970]

Amazing video, best I have seen about hyperscale.

[@Tony-dp1rl]

This was the best video on Hyperscale I have seen. Thanks!

[@NTFAQGuy]

Thanks!

[@siddhu1185]

Incredibly well-explained. Fantastic video on Hyperscale!

[@NTFAQGuy]

Appreciate it!

[@scottkim8805]

John, thanks for another great training video. you've explained this very well!!

[@NTFAQGuy]

Thanks, glad you found it helpful!

[@renatojrestorque6150]

Fantastic explanation. Thank you so much for sharing your time and this magnificent content, Chief.

[@Dikimkd]

Awesome video as always. 😎

[@NTFAQGuy]

Thanks!!!!

[@Xan7a]

Eye opening, thank you!

[@MoChowdhury-cl5hy]

Hi John, loved this video so much that I watched it twice :-) great explanation and deeper dive into this architecture option for Azure SQL

[@NTFAQGuy]

Glad you enjoyed it!

[@rameshlovesmusic]

thanks a lot for explaining it in detail.

[@NTFAQGuy]

Great to hear you found it useful!

[@Wonderscope1]

Hey John, Thank you for the fantastic video! It’s incredible how you simplify complex topics. I have a couple of comments: Please be mindful of backup costs. The video mentioned that the cost includes only vCore and Data Storage, but backups aren’t free and can increase rapidly depending on the configured retention policies. It’s challenging to estimate these costs until production-level transactions are running on the database. You mentioned that it’s possible to configure vCore for each database. I thought it could only be configured once for all databases. Could you provide more details on configuring vCore for individual databases? Thanks!

[@joseramonlopez1113]

I see myself using it in no time

[@windyearle]

Thing is, when would you want to failover, other than if the data center or region was down? -- in which case a Microsoft-managed failover will work just fine.

[@NTFAQGuy]

There are many smaller scale issues that can impact a subset of services without the whole region being down.

[@MaxHRO]

I'm interested in the possibility to use Confidential Computing as hardware configuration (Shown at video position 15:05 ff). This configuration is shown but not selectable on my environment. What is to do to make this available? Additional resource providers? Maybe is it in preview, quotas are missing or simply not available in european regions?

[@VirtualPackets]

Hi John, so does the Geo Replica take care of the Blob seed as well? I take that's it's a one time seed and then it uses the log service (forward) to sync any additional updates and writes back to the local blob storage in region 2. Great session 👻

[@NTFAQGuy]

Blob snapshot for initial seed then log forward.