Skip to main content
Server Fault

Return to Question

deleted 49 characters in body
Source Link
lansalot
lansalot
  • 11
  • 2

So, in my MSDN subscription, myself and a developer set up an Azure SQL 480mb database to test performance, initially on the vcore model. Charges very quickly accrued and despite practically nothing being done with the database beyond the initial load and a couple of performance tests, we were at the £17 mark within a day or two! Yikes.. so we experimented with Basic DTU, Standard S0 and S1 and settled on S1 9DTU20) as being ideal. Today, I log in to the portal to find my vcore (gen5) charges have more than doubled to nearly £34! This is despite nobody using it at all (the developer was on leave, and I was busy elsewhere).

Can anyone advise what's going on here?

single general purpose - serverless - compute gen5 vcore vcore 33£33.6851728317913168 single standard s0 dtus £ 2.44243457732118844 single standard s1 dtus £ 1.46546237500000246 single/elastic pool general purpose - storage data stored £ 0.1405295438263514 single basic b dtus b dtus £ 0.01248391666666601

You can clearly see our changes/trials with basic, S0 and S1 (settled on S1)- so why is vcore still increasing as well?

Thanks for any insight

So, in my MSDN subscription, myself and a developer set up an Azure SQL 480mb database to test performance, initially on the vcore model. Charges very quickly accrued and despite practically nothing being done with the database beyond the initial load and a couple of performance tests, we were at the £17 mark within a day or two! Yikes.. so we experimented with Basic DTU, Standard S0 and S1 and settled on S1 9DTU20) as being ideal. Today, I log in to the portal to find my vcore (gen5) charges have more than doubled to nearly £34! This is despite nobody using it at all (the developer was on leave, and I was busy elsewhere).

Can anyone advise what's going on here?

single general purpose - serverless - compute gen5 vcore 33.68517283179131 single standard s0 dtus 2.442434577321188 single standard s1 dtus 1.465462375000002 single/elastic pool general purpose - storage data stored 0.14052954382635 single basic b dtus 0.012483916666666

You can clearly see our changes/trials with basic, S0 and S1 (settled on S1)- so why is vcore still increasing as well?

Thanks for any insight

So, in my MSDN subscription, myself and a developer set up an Azure SQL 480mb database to test performance, initially on the vcore model. Charges very quickly accrued and despite practically nothing being done with the database beyond the initial load and a couple of performance tests, we were at the £17 mark within a day or two! Yikes.. so we experimented with Basic DTU, Standard S0 and S1 and settled on S1 9DTU20) as being ideal. Today, I log in to the portal to find my vcore (gen5) charges have more than doubled to nearly £34! This is despite nobody using it at all (the developer was on leave, and I was busy elsewhere).

Can anyone advise what's going on here?

single general purpose - serverless - compute gen5 vcore £33.68 single standard s0 dtus £ 2.44 single standard s1 dtus £ 1.46 single/elastic pool general purpose - storage data stored £ 0.14 single basic b dtus £ 0.01

You can clearly see our changes/trials with basic, S0 and S1 (settled on S1)- so why is vcore still increasing as well?

Thanks for any insight

Source Link
lansalot
lansalot
  • 11
  • 2

Azure SQL database still incurring vcore charges despite move to DTU?

So, in my MSDN subscription, myself and a developer set up an Azure SQL 480mb database to test performance, initially on the vcore model. Charges very quickly accrued and despite practically nothing being done with the database beyond the initial load and a couple of performance tests, we were at the £17 mark within a day or two! Yikes.. so we experimented with Basic DTU, Standard S0 and S1 and settled on S1 9DTU20) as being ideal. Today, I log in to the portal to find my vcore (gen5) charges have more than doubled to nearly £34! This is despite nobody using it at all (the developer was on leave, and I was busy elsewhere).

Can anyone advise what's going on here?

single general purpose - serverless - compute gen5 vcore 33.68517283179131 single standard s0 dtus 2.442434577321188 single standard s1 dtus 1.465462375000002 single/elastic pool general purpose - storage data stored 0.14052954382635 single basic b dtus 0.012483916666666

You can clearly see our changes/trials with basic, S0 and S1 (settled on S1)- so why is vcore still increasing as well?

Thanks for any insight