E
erinstellato
Hello SSMS users! A short post today to remind folks to check out the feedback site regularly. As I mentioned in a previous post, I started a Friday Feedback series on LinkedIn. I know that not everyone uses LinkedIn, and I want to make sure that you, as a SSMS user, are taking the opportunity to provide your opinion, as your votes and comments contribute to the direction of SSMS moving forward.
The most recent topics we’ve covered are listed below. Please review these ideas and vote! If you can find time to peruse other ideas to see what resonates with you, and then vote and/or comment, that’s even better. Bonus points if you share this information with your colleagues and encourage them to check out the feedback site!
I also asked about one topic for which there is no feedback item: database maintenance. I was interested in understanding whether folks use maintenance plans, third-party scripts, or custom scripts developed internally. Feel free to comment on this post to share that information.
We are interested in understanding what capabilities you want to see if we had a copilot in SSMS. Providing specific scenarios or examples of where a copilot would be useful in your workload are extremely helpful, feedback item: Integrate Copilot / ChatGPT for SQL Server Management Studio - Create SQL scripts or re-write existing scripts
There are multiple gaps in SSMS as it relates to Azure SQL DB – cases where the UI functionality available for an on-premises SQL Server isn't the same (or doesn't exist) for an Azure SQL DB. Help us understand what gaps affect you the most! There are a couple examples below, but if you don’t find a feedback item for your specific scenario, please create one. It’s likely that other folks have the same challenge.
I completely underestimated responses related to compatibility level – the amount of frustration that surrounds it runs deep and that's fair. We do not have the ability to change how SSMS and SQL use compatibility level. But we can try to provide clarification in the compatibility level list. I created a feedback item with a list of options – please review and comment: Reduce confusion with the database compatibility level list
The SSMS 21 release will provide support for extensions. I need to note that we probably will not have a marketplace for extensions immediately. There are a lot of moving parts for SSMS 21, and while we’re doing our best to keep everything trending in the same direction, it’s tricky. I’ll ask for patience now! However, understanding what existing Visual Studio extensions you all would want to see in SSMS would be helpful. There are two that I am aware of (linked below), but for others, please create a feedback item (e.g. “Add SSMS support for the ZZZZ extension” and include the extension name). Please make sure you search before you create a new item!
If you have ideas for new extensions, that’s great, those need their own (new) feedback item. As we move toward a more extensible SSMS, it provides an opportunity for folks in the community to create new extensions (and open source for wider collaboration).
Continue reading...
The most recent topics we’ve covered are listed below. Please review these ideas and vote! If you can find time to peruse other ideas to see what resonates with you, and then vote and/or comment, that’s even better. Bonus points if you share this information with your colleagues and encourage them to check out the feedback site!
I also asked about one topic for which there is no feedback item: database maintenance. I was interested in understanding whether folks use maintenance plans, third-party scripts, or custom scripts developed internally. Feel free to comment on this post to share that information.
Copilot in SSMS
We are interested in understanding what capabilities you want to see if we had a copilot in SSMS. Providing specific scenarios or examples of where a copilot would be useful in your workload are extremely helpful, feedback item: Integrate Copilot / ChatGPT for SQL Server Management Studio - Create SQL scripts or re-write existing scripts
Missing functionality for Azure SQL DB in SSMS
There are multiple gaps in SSMS as it relates to Azure SQL DB – cases where the UI functionality available for an on-premises SQL Server isn't the same (or doesn't exist) for an Azure SQL DB. Help us understand what gaps affect you the most! There are a couple examples below, but if you don’t find a feedback item for your specific scenario, please create one. It’s likely that other folks have the same challenge.
- Implement better support for Azure databases in Central Management Server
- Sql Server Management Studio Enhancement - Alias for Azure SQL connections
Changing the values in the compatibility level drop down
I completely underestimated responses related to compatibility level – the amount of frustration that surrounds it runs deep and that's fair. We do not have the ability to change how SSMS and SQL use compatibility level. But we can try to provide clarification in the compatibility level list. I created a feedback item with a list of options – please review and comment: Reduce confusion with the database compatibility level list
Extensions in SSMS
The SSMS 21 release will provide support for extensions. I need to note that we probably will not have a marketplace for extensions immediately. There are a lot of moving parts for SSMS 21, and while we’re doing our best to keep everything trending in the same direction, it’s tricky. I’ll ask for patience now! However, understanding what existing Visual Studio extensions you all would want to see in SSMS would be helpful. There are two that I am aware of (linked below), but for others, please create a feedback item (e.g. “Add SSMS support for the ZZZZ extension” and include the extension name). Please make sure you search before you create a new item!
If you have ideas for new extensions, that’s great, those need their own (new) feedback item. As we move toward a more extensible SSMS, it provides an opportunity for folks in the community to create new extensions (and open source for wider collaboration).
Continue reading...