This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 95%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
Hi everyone.
Where does one report SQL Server or T-SQL bugs now that UserVoice is gone? What is the replacement Microsoft, as it relates to SQL Server?
Connect is gone.
UserVoice is gone.
I had quite a few entries logged in personally in both.
Where is the history?
Where to log this stuff now?
Any ideas?
Is there any voice left that SQL community can raise that Microsoft can hear?
Thanks
Vladimir
Welcome to Microsoft Q&A!
You could refer SQL Server help and feedback which explains different ways to get assistance with your issue, or provide feedback for either SQL Server, or the SQL Server technical documentation.
You could consider to open a ticket with Microsoft support if you have any urgent issue or concern.
Thank you for understanding!
Best regards,
Melissa
Hi.
Thanks for your link. I am aware of many of those venues, however, Connect and UserVoice served different purpose.
It served as non-emergency, general feedback channel that SQL community could use to submit issues.
Reading from that link, it was a channel to... "Feedback suggestions
You can submit suggestions for improvement, as well as submit bugs for:" ... SQL Server, SSMS, T-SQL.
In SSMS, when user runs query with geometry data type output, and result set includes set extra column value for label, there is a bug that I submitted recently, couple weeks ago, and that bug is in the fact that geometry label is not drawn, unless one unchecks and checks to show grid lines. I do not need immediate resolution; I have no desire to call paid support lines to report it, spending days on it. I moved on with my life in hopes that this issue will be read, triaged, and fixed one day.
That is the type of issue Connect/UserVoice is good for.
Removing UserVoice, which was poor substitution for Connect, without providing any replacement, when Microsoft promised replacement with an announcement on UserVoice, is poor decision for a company like Microsoft.
Just like trying to deprecate diagram support or removing debugger!
I am flabbergasting at such decisions and expect better from Microsoft.
There was a lot of good will in SQL community towards Microsoft, however Microsoft is killing it by thousand cuts, with decision like this.
You can pass it to your bosses if you can.
Thank you personally for your help to 1000s of users on this site.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
In MS defense, the Connect/Feedback/UserVoice have never been good for them or the user community.
There are many duplicate and non-issues reported by users in those methods. They need to have a MS employee "groom" them and add them to the list, rather than just allow anyone to post on it.
Certainly there are real issue. But if you are having an issue, your first response should be to upgrade to a current patch level and retest. If that does not work, contact MS Support.
I beg to disagree about its usefulness.
Connect was a lot better as it was more structured, and users had to specify lots of appropriate details before posting.
UserVoice didn't have that structure and allowed lots of useless and non-sense entries. In other words, it became dumping ground.
It was squarely Microsoft fault for allowing this mess.
However, it was the only venue for appropriate stuff too.
And it seems to me Microsoft didn't get appropriate level of resources assigned to this channel to quickly tirage those entries.
At over 10,000 entries they seem to be overwhelmed. Or just stopped caring about it all together. There were less than 100 entries in triaged state.
What about user product specific suggestions?
Is calling paid product support with credit card in hand to talk to some jr. Microsoft employee about any new idea a user may have, is really a way now?
What about others upvoting an idea because it is important to others too?
Does MS expect others to also call paid MS support so they can up-talk someone's idea?
This does not sound like the right venue for community feedback.
I have used MS SQL Server product support. It's a hassle and lots of trouble to get through people that understand the issue.
If MS cares to have worldwide community have any say as to what they want/need/expect/suggest SQL Server have, they need something like product specific Connect, open to public.
Otherwise, there is a danger to lose touch with reality.
In SSMS, when user runs query with geometry data type output, and result set includes set extra column value for label, there is a bug that I submitted recently, couple weeks ago, and that bug is in the fact that geometry label is not drawn, unless one unchecks and checks to show grid lines. I do not need immediate resolution; I have no desire to call paid support lines to report it, spending days on it. I moved on with my life in hopes that this issue will be read, triaged, and fixed one day.
That is the type of issue Connect/UserVoice is good for.
Just because UserVoice is not available anymore does not mean that all those bug reports have been flushed down the toilet. They are still there in Microsoft's internal bug-tracking system, in some shape or form.
Again, I urge you to cool down. While the messaging on the current site certainly could be clearer, we don't know how long this hiatus will be. If a new site is up in two weeks, is it the end of the world that we are not able to report bugs for two weeks?
If it's three months later and there is still no update, it's a different matter.
Right now UserVoice(feedback.azure.com) has been decommissioned and its replacement will be online in mid-October 2021.
If you have any wish to make feedback requests about SQL Server in the meantime, please provide us all the information listed below and we are glad to submit it on behalf of you.
Title:
Technical Feedback(Describe the precise feedback. Please avoid entering PII(Personally Identifiable Information)):
Business Scenario and Desired Outcome:
Issue Impact:
Workaround details if there are any:
Please be sure to explain things as much as possible, thanks for your patience.
Best regards,
Melissa
A new feedback site is now available at https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0.
Old items, including votes!, appear to have been migrated.
Ernald,
Thanks for posting a link here. I discovered it independently today, however, you have provided an answer to my original question!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 57.99999999999999%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETW%3C/text%3E%3C/svg%3E)
Furthermore, the smiley face in the upper left corner of the installer actually takes the user to exactly that place. It took hours before I noticed though.
Visual Studio seems to be more user-friendly. It's much easier to report bugs, make suggestions, etc.
Within SSMS, I notice that clicking:-
These aren't obscure bugs hidden deep within some little-used functionality. These are top level, "page 1" flaws that are not being addressed.
I see this in 18.10 which was released on Oct 5th, when the new feedback site was still not available. One can question why they kept the old link - but maybe the SSMS team naïvely imagine that there would be a redirection to the new site once it became available. Bear in mind that Microsoft is a large companies, and in large organisations, the left hand does not always know what the right hand is up to.
As for the Resource Center, bear in mind that SSMS is based on the Visual Studio 2017 shell, so I don't think having SSMS to start use Edge is a simple thing, but something which will not be addressed until SSMS moves to a newer version of the VS Shell.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more