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