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
1 months agoWilliam
1 months agoAvery
4 days agoShantay
10 days agoLeah
2 months agoLisha
22 days agoAlbina
29 days agoStephanie
1 months agoDanilo
1 months agoTammy
1 months agoCletus
1 months agoDaron
2 months agoStephaine
2 months agoThora
20 days agoCherry
28 days agoBrittani
1 months agoElli
2 months agoLelia
3 months agoJaime
3 months agoOneida
3 months ago