azure-sdk-for-net
azure-sdk-for-net copied to clipboard
Azure
[FEATURE REQ] There doesn't appear to be a Quota API for Azure SQL Databases (and Logical Servers)
Library name
Azure Quota Service API
Please describe the feature.
There is currently no way to determine your quota or utilization of Azure SQL Databases (and Logical Servers) in an Azure subscription. The current limit is 250 per region, per subscription as defined at https://learn.microsoft.com/en-us/azure/azure-sql/database/resource-limits-logical-server?view=azuresql. However, the Azure Portal UI limits you to 200. This is likely a UI bug. Nevertheless, there is no Quota API that can be used to determine or change the current state.
Hi @sdavis3. Thank you for reaching out and we regret that you're experiencing difficulties. Unfortunately, this repository is focused on the Azure SDK for .NET - we're unable to assist with other Azure issues. Since what you're describing appears to be related to the Azure portal and not one of the SDK packages, your best path forward would be to open an Azure support request.
I'm going to close this out; if I've misunderstood what you're describing, please let us know in a comment and we'd be happy to assist as we're able.
I would respectfully disagree. I may have poorly worded it, but I used the portal as an example of how I ended up here...which may indicate a more significant problem as this information doesn't seem to exist anywhere through the stack. The SDK does not support the same functionality. It's a feature request of the SDK to add support for Azure SQL Database Quotas.
@xboxeer: Can you please confirm whether or not this exists in the REST API and, if not, advise on a path for @sdavis3 to make a service request?
Hi @sdavis3, if you want to increase the quota like on portal, you can create a support ticket with the help of Azure.ResourceManager.Support. Here is our sample about how to create a request to increase the quota of sql database server. You can refer to it, but you also need to know that this is an auto-generated sample, so using it directly might not work.
Hi, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!
With all due respect, this has been one of the most painful exercises I've ever been through with an SDK.
1.) The link shared in the reply above is not available. However, I was able to search and find the area that was being referenced. 2) The institutional knowledge needed to populate the support ticket objects with precisely the right data is extremely difficult to find out without scouring the MSLearn pages and executing various REST calls to get precisely the right GUIDs needed to populate the request.
After spending hours doing this, only to finally get the following result back from the API: "Azure.RequestFailedException: Your support plan type is Standard. To create and update support tickets, and add communication operations, you need access to our high tier-support plans." Quota API increases should not be hidden behind a support paywall. This is misguided and misplaced as the portal does not require the same to submit a Quota request.
Regardless of the above, the idea that this level of effort is needed for a simple request to increase a Quota is frustrating. The portal incorrectly limits the number of Azure SQL Servers to 200 when the limit is actually 250. The API hides quota increases behind a paywall and the SDK does not appear to address or overcome either of these concerns.
As a long-standing customer of Azure, it feels like I'm chasing ghosts here. What can I do to resolve this issue?
Hi @sdavis3, sorry for the wrong link, I forgot that we are doing some sample migration work, that's my bad. This should be the correct one.
And as a client-side tool, our SDK code is based on the API spec from the service team, we are continuing to providing more documents and samples to help the customers but here I don't see much space to improve the code itself. Back to your question, I think the better way is to create a support request on Portal about the incorrect limit number, so that the support engineer could trace and resolve this issue.