Suspected Bug: SSMS 22 Copilot integration caused massive usage spike (1,200+ requests in 1 day) #181818
Replies: 16 comments 7 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
I experienced the same issue today. I had never previously reached my Copilot quota, but after I started using SSMS, my quota was completely consumed in the same Day. Another colleague experienced the same behavior. In a single SSMS session, his entire Copilot quota was exhausted. This suggests there may be an issue with Copilot usage tracking or an unintended increase in requests triggered by SSMS. |
Beta Was this translation helpful? Give feedback.
-
|
I have seen the exact same issue. Copilot in SSMS flies though the premium requests. |
Beta Was this translation helpful? Give feedback.
-
|
I also experienced the same. Earlier it was working fine even in SSMS 22. But yesterday it suddenly started consuming too much premium requests for Github copilot pro. For every chat it is consuming 30-40 requests whereas earlier it was consuming one request for one chat prompt. |
Beta Was this translation helpful? Give feedback.
-
|
I also experienced the same |
Beta Was this translation helpful? Give feedback.
-
|
I've seen this too - I did what I thought was innocent chat, but it made me exceed my quota significantly. I was at 50% usage and now well into paid overages. From now I am going to use free models in SSMS or just not use it at all. |
Beta Was this translation helpful? Give feedback.
-
|
I believe this is what happened to me today :( |
Beta Was this translation helpful? Give feedback.
-
|
I also had the same issue, I actually raised a ticket on GitHub thinking they had a billing incident but after they sent me the consumption data extract it was easy to tell this was coming from SSMS. This makes copilot unusable in SSMS and its one of those cases where its very hard to understand how Microsoft ships code like this, the same feature is working ok in Visual Studio and is working great in VS Code. For me it's mind blowing that the free open source vscode is so much better than the other tools :)... |
Beta Was this translation helpful? Give feedback.
-
|
I've had this happen too without even using the chat in SSMS 22. Claude sonnet 4.5 model line usage going vertically up without using any paid models for a few days. |
Beta Was this translation helpful? Give feedback.
-
|
You can request billing incident to check and see .. |
Beta Was this translation helpful? Give feedback.
-
|
Hey folks - PM for GitHub Copilot in SSMS here, I was just made aware of this discussion so apologies if it looked like we were not paying attention. Issues and suggestions for SSMS (and also GitHub Copilot in SSMS) should be logged on the SSMS feedback site. We are aware of this problem and are working on a resolution. If you have additional questions, feel free to tag me in a reply. I don't think we need any additional logs at this moment, but if that changes, I'll let you all know. |
Beta Was this translation helpful? Give feedback.
-
|
Confirmed Bug in SSMS 22: Recursive API Loop causing Quota Depletion (Case Resolved) The Incident: Last Wednesday, I asked a prompt to Copilot in SSMS 22.2.1 just before leaving the office. Within just one hour after I left, my personal Premium requests (300/300) were completely depleted, and an additional $10.00 USD was billed due to a recursive background loop that continued while I was away. Resolution: I managed to resolve this by coordinating between GitHub and Microsoft (with the help of Gemini to organize the evidence). GitHub Support: They were very helpful and issued a one-time $10.00 credit and reset my usage as a courtesy once I provided the evidence. Microsoft: They have acknowledged the report and marked it as "Under Investigation". Temporary Workaround (Self-Protection): Until a formal patch is released, I’ve advised my team to completely close the SSMS application before leaving their workstations. This seems to be the only reliable way to kill the background process and prevent infinite API calls overnight. Hope this helps the PM team @erinstellato-ms in narrowing down the root cause! |
Beta Was this translation helpful? Give feedback.
-
|
https://developercommunity.visualstudio.com/t/Critical-Bug-SSMS-22-Copilot-Agent-tri/11040048 |
Beta Was this translation helpful? Give feedback.
-
|
@RicoLeeTW I greatly appreciate you following up and sharing this update. From our side, I had mention that we're working on the problem and a resolution. This required some code changes which have been checked in, but now we need to test to make sure we haven't regressed anything, and that we have fixed the issue. As soon as we have a fix ready for a release, I will follow up. Thanks again for keeping us in the loop. |
Beta Was this translation helpful? Give feedback.
-
|
I asked GitHub support for a credit but they said that this feature is in preview and they wouldn't. Who or where should I to to get a credit. After the response I was considering uninstalling ssms. |
Beta Was this translation helpful? Give feedback.
-
|
Mm too feature is in preview |
Beta Was this translation helpful? Give feedback.
-
|
@ocdi @457shop I'm trying to find a contact on the GitHub side to assist. Thus far I haven't had any luck but will follow up here when I do have more information. |
Beta Was this translation helpful? Give feedback.
-
This is a horrible customer experience. Microsoft should give any user who uses copilot from smss an apology and a free year subscription to copilot |
Beta Was this translation helpful? Give feedback.
-
|
This just happened to me today!!!! I see you reported this last December. It is UNFORGIVABLE that this has not been resolved yet. We are not even warned about it! What a diabolically terrible service! |
Beta Was this translation helpful? Give feedback.
-
|
Not only was this a horrible experience. I also have to surrender my valuable tokens in the process. Sorry this is not an “in preview” feature nor can Microsoft and GitHub get into a blame game. Microsoft is rapidly pushing us to “copilot everything” and owns GitHub. “I can’t find a contact at GitHub”? Give me a break. |
Beta Was this translation helpful? Give feedback.
-
|
We released a fix for this issue today, in SSMS 22.3.2. Install the most recent release from here. @easis @ocdi @johnhenley @badrshs @RicoLeeTW If any of you have reached out to GitHub but have not been refunded for lost credits, please email me directly. My email address is my first name and then my last name (all one word) and then at microsoft dot com. I will work with you directly to get that resolved. Also, please note we've documented a known issue with GPT Codex models, but during some further testing, I'm seeing that all GPT 5 models are having issues. We do not recommend using GPT 5 models at this time. Let me know if you have questions, thank you for providing valuable feedback to help improve the product. |
Beta Was this translation helpful? Give feedback.
-
@wardboumans Please see information below, if you haven't already tried to contact GitHub directly. |
Beta Was this translation helpful? Give feedback.
-
|
Can we get a refund for this? It wasted our $100 in like one hour... Thanks Microsoft! 
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Copilot Feature Area
Account Related
Body
Hi everyone,
I'm posting here for visibility because I opened a support ticket 10 days ago regarding a severe billing anomaly and haven't received a response yet.
The Issue: On Dec 4th, I noticed my Copilot Pro+ usage was already at 88%. Upon analyzing my billing report, I found a massive spike of 1,202 requests made with Claude Sonnet 4.5 in a single day (approx. Dec 2nd).
Why this is an error:
Suspected Culprit: I believe this was caused by the new SSMS 22 (SQL Server Management Studio) Copilot integration.
Has anyone else experienced usage leaks with SSMS 22? I am looking for support to investigate this bug and reset my monthly quota, as this was clearly not legitimate user activity.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions