I feel like an Azure SQL Database managed instance could work too, but I’m a bit confused about how it compares to the elastic pool in terms of scaling.
I think using an Azure SQL Database elastic pool could be a good option since it allows for dynamic scaling, but I'm not entirely sure about the downtime aspect.
I'm pretty confident the answer is A - an Azure SQL Database elastic pool. That's designed for scenarios just like this, where you need to scale resources up and down based on workloads. The other options don't seem to fit the requirements as well.
Okay, let's see. We need to move two 100-GB databases to Azure and be able to scale resources dynamically. I'm leaning towards an Azure SQL Database managed instance - that should give us the flexibility we need while minimizing downtime.
Hmm, I'm not sure about this one. I'll need to think through the requirements carefully - minimizing downtime during scaling is important. Maybe SQL Server on Azure VMs could work, but I'm not confident that's the best solution.
I think the key here is to find a solution that can dynamically scale resources based on workloads. Azure SQL Database elastic pool seems like a good option for that.
Option B? Are you kidding me? Hosting SQL Server on a VM? That's so 2010. I want the full power of the cloud, not some half-baked solution. Definitely going with option A!
Option C seems promising, but I'm not sure if I want to deal with the added complexity of a Managed Instance. Might as well keep it simple with option A and the elastic pool.
Hmm, I'm not sure about option A. What if my databases have different scaling requirements? Wouldn't it be better to go with option D and have two single Azure SQL databases instead?
I think option A is the way to go. Elastic pools allow me to dynamically scale resources based on workloads, and minimize downtime during scaling operations. Sounds like the perfect fit for my databases.
User 1: I think option A is the way to go. Elastic pools allow me to dynamically scale resources based on workloads, and minimize downtime during scaling operations. Sounds like the perfect fit for my databases.
Lemuel
3 months agoJaclyn
3 months agoDalene
4 months agoGertude
4 months agoSlyvia
4 months agoAmie
4 months agoJovita
4 months agoLeila
5 months agoJaclyn
5 months agoDaron
5 months agoFlo
5 months agoArgelia
5 months agoLennie
5 months agoGerman
5 months agoAvery
5 months agoValentine
10 months agoWilliam
10 months agoBulah
8 months agoAvery
9 months agoShantay
9 months agoLeah
10 months agoLisha
9 months agoAlbina
9 months agoStephanie
10 months agoDanilo
10 months agoTammy
10 months agoCletus
10 months agoDaron
10 months agoStephaine
11 months agoThora
9 months agoCherry
9 months agoBrittani
10 months agoElli
10 months agoLelia
11 months agoJaime
11 months agoOneida
11 months ago