I created a brand new, free (100k vcore/32GB) Azure SQL Database, but even though nothing is using it, it's draining my vCores remaining.

Question

I created a brand new, free (100k vcore/32GB) Azure SQL Database, but even though nothing is using it, it's draining my vCores remaining.

Pete 25

I created a brand new, "free" (100k vCore/32GB) Azure SQL Database, but even though nothing is using it, it's draining my vCores remaining. I don't even have any tables yet. No connections to it. Nothing. Yet my remaining vCores are steadily reducing. I'm thinking it's storage usage, but since I haven't enabled "Continue using database for additional charges" I am unable to change the storage size or enable pausing. Is this the intended behavior? I ask because I'm still developing and I'm worried that by the time I'm ready to use the database, I'll have no remaining free usage. usage

Accepted answer

0 additional answers

Your answer

Answer 1

TP 123.2K Volunteer Moderator

Hi Pete,

From your description what you are experiencing is not normal.

When you create Azure SQL Database Free database offer it should be set to auto-pause in 1 hour. If you don't connect to it or do anything that would prevent auto-pausing, the database should switch to Paused (you can see this on Overview blade) in a little over an hour after creation, and all vCore second charges should stop.

Please reference below article for reasons why database will resume and troubleshooting auto-pause:

https://learn.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview?view=azuresql&tabs=general-purpose#auto-pausing-and-auto-resuming

Since we are at beginning of month the 100,000 seconds has reset so you should try to resolve the issue as soon as possible to preserve most of your free seconds. If I know I'm not going to use the free database for a while I set Max vCore to 1 and Min to .5 just in case it resumes to limit how fast it depletes seconds. Not a solution to your issue but I thought I would mention it.

If the troubleshooting document above doesn't fix it for you I would suggest you delete the database and server (I'm assuming you have no data yet) and re-create it fresh, trying to leave everything as default. After it has finished creating, wait about 1½ hours and then verify that it is Paused.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Pete 25 Reputation points

2023-12-01T13:06:02.9133333+00:00

Thanks for the response TP. I've actually already seen that article and non of the suggested actions helped. To make things worse, even though I was on December's "free" month (showing over 90k remaining vCores) I have been charged $2.38. I know that's not a lot but I only had the database up a few hours, with absolutely nothing in it and nothing connected to it, on a FREE plan. This is exceptionally frustrating. I had to destroy the resource to try and stop the bogus charges. I've opened a case with support. Hopefully they can shed some light on this.
TP 123.2K Reputation points Volunteer Moderator

2023-12-01T13:24:28.8033333+00:00

Understand, I would be frustrated as well. What exactly are they charging you for? If I go in to my subscription -- Cost Analysis -- View -- Smart views -- select Resource groups -- click Resource groups -- expand the resource group with my free database, click on the database, expand SQL Database, I see below details:

It's showing $0 for me but I'm curious what specific product they are charging you for?
Pete 25 Reputation points

2023-12-01T13:56:39.1333333+00:00

First off, thank you for showing me this cost breakdown, that's very helpful. What's strange is it's showing 2 databases? I created the first one on Tuesday, few days ago, on the free plan, but on Thursday I was notified I reached my limit. I had a tiny, 1 row table. I researched and I think it's because I left ssms connected to it, not sure though. So yesterday afternoon, I deleted the resource, and set it to not charge for overages. I stopped my webapp and shutdown ssms. There were no tables or connections, but my vCores were still draining and my charges were steadily increasing. It looks like something got messed up on their end and were still charging me for a deleted resource?
Pete 25 Reputation points

2023-12-01T13:56:59.1866667+00:00
Pete 25 Reputation points

2023-12-01T14:44:17.9233333+00:00

I'm a little timid to start messing around and experimenting until I hear from support, but just so I'm clear, if I was to create a brand new Azure SQL Database, apply the free offer, and leave it alone (no connections, no tables/data, etc) then I shouldn't see my vCore credits draining correct? Is there a way to drill down and see exactly what is using the vCores? I've seen the articles suggesting to look at spwho2 but in my situation, I never connected anything to it.
TP 123.2K Reputation points Volunteer Moderator

2023-12-01T15:40:58.2233333+00:00

Yes, assuming you still have free vCore seconds left for December, if you create new free database with defaults and leave it alone, you should see it switch to Paused in roughly 1+ hour after creation. I went back in history and it looks like mine used vCore seconds for about 1hr 4 minutes or around there after I created it.

Unsure what happened. I think it is possible if you exhaust all the free vCore seconds, delete the database, create new free database, it may bill you for the "new" used vCore seconds even though the portal shows that you are on free. Even if that is true, it doesn't explain why your second database didn't auto-pause after an hour. Note I don't know how it works in this case for a fact so treat this paragraph as speculation.

In the usage details you can see precisely what/when those charges in Cost Analysis are from. In this way you could tell if it was the second database you created that generated the charges or the first. It's easy to get the details after invoice is generated, but getting (non-billed entries) right now is tough (for me) due to a change they made. I need to re-write some code to pull the details since the previous methods are broken.

I've not experienced it personally, but people have complained in the past that their serverless database didn't auto-pause even though it should have.
TP 123.2K Reputation points Volunteer Moderator

2023-12-06T19:46:13.7466667+00:00

@Pete Any update?
Pete 25 Reputation points

2023-12-06T21:47:08.32+00:00

Hey TP, no, not yet. I'm still waiting on support to investigate. I'm not confident that they'll be able to explain it. I'm trying to recreate the issue but so far, the 1hr Auto-Pause delay is activating and not burning my vCore credits. I'll give support another week and if they don't provide any insight, I'll close this thread and give you the credit. Thanks again for all your assistance.
Pete 25 Reputation points

2023-12-14T14:06:13.1333333+00:00

Hey TP, after finally talking to SQL Support, they stated that because I deleted the instance (to prevent the erroneous charges from accruing) the logs are gone and they aren't able to troubleshoot the root cause. They refunded my account but aren't able to shed any light on what happened. I did re-build the exact same recourses and they are performing exactly as expected, so that's good. Thanks again for all your help, I'll mark your answer as accepted, to give you credit for helping.
TP 123.2K Reputation points Volunteer Moderator

2023-12-15T17:04:12.9966667+00:00

Thanks for the follow up letting me know what happened.

Share via

I created a brand new, free (100k vcore/32GB) Azure SQL Database, but even though nothing is using it, it's draining my vCores remaining.

0 additional answers

Your answer