Skip to main content
Solved

Azure default pricing tier setting


Forum|alt.badge.img+2

When creating a new azure database from the creation menu it's automatically created in the highest pricing tier. This is since the Create database query uses the default gen5 tier.

There seems to be no way to set a default pricing tier in azure. But you can use a parameter with the create database query to set the pricing tier.

Is there any way to set the default pricing tier in the SF or fill in the service_objective parameter of the create database query?

Related topic on microsoft forums: https://social.msdn.microsoft.com/Forums/en-US/fd294936-06fa-4c23-aa11-d0b6836df56e/set-the-default-pricing-tier-for-newly-created-databases?forum=ssdsgetstarted

 

Best answer by Mark Jongeling

Hi Anne, I have discussed just now and we advise using a Manual control procedure to Alter the created database to use the correct Service objective by using the following code:

ALTER DATABASE [DBName] MODIFY(EDITION='Standard', SERVICE_OBJECTIVE='S0')

We will investigate how to do this automatically in coherence with Indicium.

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

2 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Anne,

I can understand it will become quite pricey when developers start making databases using the highest pricing tier. I will discuss this internally with my colleagues on how we can be of assistance. 


Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3945 replies
  • Answer
  • October 19, 2021

Hi Anne, I have discussed just now and we advise using a Manual control procedure to Alter the created database to use the correct Service objective by using the following code:

ALTER DATABASE [DBName] MODIFY(EDITION='Standard', SERVICE_OBJECTIVE='S0')

We will investigate how to do this automatically in coherence with Indicium.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings