question

ArindamPaulRoy-3175 avatar image
0 Votes"
ArindamPaulRoy-3175 asked KalyanChanumolu-MSFT edited

Cheapest Highly Available SQL Server Option on Azure

Hi

My requirements are as follows :-

a) A highly available (not across zones) low volume (less than 1k requests a day) SQL Server database on Azure

b) Cheapest price in view of (a)

What flavor of the gamut of SQL Server options on Azure will meet this?

azure-sql-database
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

KalyanChanumolu-MSFT avatar image
0 Votes"
KalyanChanumolu-MSFT answered KalyanChanumolu-MSFT edited

@ArindamPaulRoy-3175 Welcome to Microsoft Q&A forums.

For the workload you are describing, you should consider Azure SQL Database serverless
You can decide the auto pause duration according to the traffic and significantly save on costs when the database is not utilized.

Please let us know if you have further questions.


If an answer is helpful, please "Accept answer" or "Up-Vote" which might help other community members reading this thread.

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi

Thanks.

From a performance perspective, would the serverless option be okay?
Are there any mitigation strategies?

0 Votes 0 ·

@ArindamPaulRoy-4561 Serverless can be Auto scaled just like any other SKU.
So, you shouldn't have performance concerns.

What mitigation scenarios are you looking for? DR, High availability, backups are all handled just like Azure SQL Database


If an answer is helpful, please "Accept answer" or "Up-Vote" which might help other community members reading this thread.

1 Vote 1 ·

Hi Kalyan

Thanks.
I meant mitigation for query performance issues just by virtue of being server-less - if that is indeed a concern.

0 Votes 0 ·

@ArindamPaulRoy-4561 When the database goes into Paused state, the first call to the database will fail. But it will warm up the database.
You need to have a retry logic in your code to reattempt the connection in case of failure.
Other than that, it is as good as using Azure SQL database.

You can easily enable this in your code

  services.AddDbContext<YourDbContext>(options =>
             {
                 options.UseSqlServer(configuration.GetConnectionString("YourDatabaseConnection"), options => options.EnableRetryOnFailure(2));
             });

Please mark as answer if the discussion was helpful

1 Vote 1 ·