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.
Valentine
20 days agoWilliam
24 days agoLeah
1 months agoLisha
1 days agoAlbina
9 days agoStephanie
15 days agoDanilo
16 days agoTammy
18 days agoCletus
22 days agoDaron
1 months agoStephaine
2 months agoCherry
7 days agoBrittani
20 days agoElli
27 days agoLelia
2 months agoJaime
2 months agoOneida
2 months ago