Microsoft
MicrosoftPablo_Lerner I hear your feedback. I am guessing (and I am simply guessing), that this statement from you:
"I do understand that there is a business model that Microsoft follows that implies we developers are not the important people but instead our managers who have to justify paying $50.000 licenses for a database software. And the consequence of that is that development of SSMS will always lack in regards of our needs and wishes."
Is based on the history of what you have seen with SSMS releases.
If so, I hope that with time you will see that is not the case. The SQL team as a whole is very interested in developers right now. And we on the SSMS team are interested in how we can improve SSMS for all users (developers, DBAs, admins, etc.). I think it would be helpful to understand more about the workflows for developers who use SSMS. For example, are folks database developers (writing T-SQL) or application developers (writing in C#, Python, etc.)?
The rate of change in SSMS may not be at the speed that folks would like to see. I understand that. I am aware that folks think that "because we are Microsoft, anything is possible." Theoretically that may be true, but there is a finite number of engineers, and a finite number of hours in the day. We are making a strong effort to do as much as we can as quickly as possible - while also working to maintain quality releases. Hopefully, in time, users will see our commitment and extract value from the improvements in SSMS.