You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a Linux user who has to go to great lengths to work around SSMS, an extremely dated app with decade-old bugs (like constantly forgetting passwords) who loves the VSCode ecosystem and ADS as well. I would really love to see ALL things you can only do in SSMS be migrated to either this plugin, or a separate mssql-management plugin. 3rd parties have tried this, but they're basically hooking into the SSMS .dll files to bring up modals, and none of them have replicated the simple glory that is Activity Monitor. The inability of our Linux and Mac users to be able to use these features anywhere but in an antiquated Windows-only app makes us want to migrate away from MSSQL itself. In an era where you can run mssql-server itself purely on Linux and function otherwise without any Windows components anywhere (we don't have a domain of any kind, either), this seems like a glaring hole to fix, if you want your flagship database product to grow and thrive.
The text was updated successfully, but these errors were encountered:
I am a Linux user who has to go to great lengths to work around SSMS, an extremely dated app with decade-old bugs (like constantly forgetting passwords) who loves the VSCode ecosystem and ADS as well. I would really love to see ALL things you can only do in SSMS be migrated to either this plugin, or a separate mssql-management plugin. 3rd parties have tried this, but they're basically hooking into the SSMS .dll files to bring up modals, and none of them have replicated the simple glory that is Activity Monitor. The inability of our Linux and Mac users to be able to use these features anywhere but in an antiquated Windows-only app makes us want to migrate away from MSSQL itself. In an era where you can run mssql-server itself purely on Linux and function otherwise without any Windows components anywhere (we don't have a domain of any kind, either), this seems like a glaring hole to fix, if you want your flagship database product to grow and thrive.
The text was updated successfully, but these errors were encountered: