Skip to content

Commit

Permalink
Merge pull request #32572 from erinstellato-ms/ssms21p2
Browse files Browse the repository at this point in the history
SSMS 21 Preview 2 (Release 12/10/2024)
  • Loading branch information
v-dirichards authored Dec 10, 2024
2 parents 180a138 + b8731b7 commit 280e69f
Show file tree
Hide file tree
Showing 6 changed files with 188 additions and 28 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
title: Customer Experience Improvement Program in SQL Server Management Studio
description: Learn about the Customer Experience Improvement Program in SQL Server Management Studio (SSMS).
author: erinstellato-ms
ms.author: erinstellato
ms.reviewer: randolphwest, maghan
ms.date: 12/10/2024
ms.service: sql
ms.subservice: ssms
ms.topic: troubleshooting-general
---

# The Customer Experience Improvement Program

As a Visual Studio-based application, SQL Server Management Studio (SSMS) is part of the Visual Studio Customer Experience Improvement Program (VSCEIP). The program is designed to help Microsoft improve SSMS and Visual Studio over time. This program collects information about errors, computer hardware, and how people use both applications without interrupting users in their tasks at the computer. The information collected helps Microsoft identify which features need improvement. This document covers how to opt in or out of the VSCEIP and provides information about the types of data we collect and how we use it.

## Opt out of diagnostic data collection

Given the purpose of the data we collect and the constraints on its access and retention, we recommend that you use the default privacy settings for SQL Server Management Studio and Windows. You can opt out of the program, but you're opting out of optional diagnostic data collection. Some diagnostic data collection is required to ensure SSMS is secure, up to date, and performing as expected. Required diagnostic data collection isn't affected by your choice to opt out of VSCEIP.

## Opt in or out

The VSCEIP is turned on by default. You can turn it off or back on again by following these instructions:

1. In SSMS select **Help** > **Privacy** > **Privacy Settings**.

1. The **Visual Studio Experience Improvement Program** dialog opens.

1. To opt out, select **No, I would not like to participate**, and then select OK.

1. To opt in, select **Yes, I am willing to participate (Recommended)**, and then select OK.

## Related content

- [Suggest a feature or improvement for SQL Server Management Studio 21 Preview](suggest-feature.md)
- [Report a problem with SQL Server Management Studio 21 Preview](report-problem.md)
33 changes: 33 additions & 0 deletions docs/ssms/feedback-and-troubleshooting/report-problem.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
title: Report a Problem With SQL Server Management Studio
description: Learn how to report a problem with SQL Server Management Studio (SSMS).
author: erinstellato-ms
ms.author: erinstellato
ms.reviewer: randolphwest, maghan
ms.date: 12/10/2024
ms.service: sql
ms.subservice: ssms
ms.topic: troubleshooting-general
---

# Report a problem with SQL Server Management Studio 21 Preview

You can report a problem from SQL Server Management Studio (SSMS) using the **Help** > **Send feedback** menu or by using the [SQL Feedback site](https://aka.ms/sqlfeedback). When reporting an issue, it's recommended that you search the site first to see if a similar issue exists. Expand the **Groups** menu on the feedback site and select **Tooling**. Enter relevant text or keywords in the Search dialog to find existing items for the problem.

Include as much detail as possible when describing the problem, including step-by-step instructions and information such as the version of SSMS (available in **Help** > **About**), the version of SQL, and the Operating System version and language. For any error message, include the entire text and use the **Show Details** button in the error dialog to capture complete details about the error to add to the item description.

## Idea status

After you report a problem, the Stage indicates where the issue is in its lifecycle. As we review the issue and move it along the workflow, we tag it with the corresponding stage. The various stages associated with reported ideas are listed here, along with a description of their meaning.

| Stage | Description |
| --- | --- |
| **Archived** | A status of **Archived** means the problem is no longer applicable or insufficient information was provided to recreate the problem. |
| **Completed** | **Completed** indicates that the latest product update fixes the problem. |
| **Needs More Information** | Any problem marked **Needs More Information** means we need more details to recreate the problem internally. Check the company response, where we ask for additional information about the problem. |
| **New** | **New** means the problem is newly reported by you or someone else. Action still needs to be taken. |
| **Planned** | A status of **Planned** means that we recreated the problem, logged a tracking item internally, and planned to fix the problem in a future release. |

## Related content

- [Suggest a feature or improvement for SQL Server Management Studio 21 Preview](suggest-feature.md)
35 changes: 35 additions & 0 deletions docs/ssms/feedback-and-troubleshooting/suggest-feature.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
title: Suggest a Feature for SQL Server Management Studio
description: Learn how to suggest features and improvements for SQL Server Management Studio (SSMS).
author: erinstellato-ms
ms.author: erinstellato
ms.reviewer: randolphwest, maghan
ms.date: 12/10/2024
ms.service: sql
ms.subservice: ssms
ms.topic: troubleshooting-general
---

# Suggest a feature or improvement for SQL Server Management Studio 21 Preview

Users of SQL Server Management Studio (SSMS) can submit requests for improvement or new functionality using the [SQL Feedback site](https://aka.ms/sqlfeedback) using **Help** > **Send feedback**. Submitted ideas are regularly reviewed, and SSMS users can upvote and comment on ideas they support.

When providing feedback, searching the site first is recommended to see if a similar idea exists. Expand the **Groups** menu on the feedback site and select **Tooling**. To search existing items, enter relevant text or keywords in the Search dialog.

## Idea status

After you submit a suggestion for a feature or improvement, the Stage indicates where the submission is in its lifecycle. As we consider your feedback and move it along the workflow, we tag it with the corresponding stage. The various stages associated with feature suggestions are listed here, along with a description of their meaning.

| Stage | Description |
| --- | --- |
| **Archived** | A status of **Archived** means the suggestion is no longer relevant to the current release, or there needs to be more community interest to keep the item active. |
| **Completed** | **Completed** indicates that your new feature suggestion is available in the latest product update. |
| **Declined** | A status of **Declined** means the suggestion doesn't match our overall product direction and is no longer under consideration. |
| **Needs More Information** | A feature suggestion marked **Needs More Information** means that we need more details so we can better understand your suggestion. Check the company response, where we ask for additional information to understand the request better. |
| **New** | **New** means the suggestion is newly reported by you or someone else. Action still needs to be taken. |
| **Planned** | A status of **Planned** means that your feature suggestion has a broad community impact and can improve the product experience. We have the item on our roadmap and the feedback item is updated when release information is available. |
| **Under Review** | **Under Review** indicates that the feature suggestion is in the queue for prioritization. Considering the product roadmap, we prioritize features to bring the best value to the broader community. Even if we don't implement your new feature suggestion immediately, we'll continue to monitor your idea, let the community weigh in, and then decide on the next steps. |

## Related content

- [Report a problem with SQL Server Management Studio 21 Preview](report-problem.md)
17 changes: 7 additions & 10 deletions docs/ssms/ssms-21/known-issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,12 @@ description: Learn about known issues in SQL Server Management Studio (SSMS).
author: erinstellato-ms
ms.author: erinstellato
ms.reviewer: randolphwest, maghan
ms.date: 11/25/2024
ms.date: 12/10/2024
ms.service: sql
ms.subservice: ssms
ms.topic: troubleshooting-general
---

# Known issues in SQL Server Management Studio 21 Preview

[!INCLUDE [sql-asdb-asdbmi-asa](../../includes/applies-to-version/sql-asdb-asdbmi-asa.md)]
Expand All @@ -19,20 +20,16 @@ This page lists known issues for [!INCLUDE [ssms-21-md](../includes/ssms-21-md.m
| --- | --- | --- |
| Analysis Services | There's currently no support for Analysis Services in [!INCLUDE [ssms-21-md](../includes/ssms-21-md.md)]. | Use SSMS 20.2 to connect to Analysis Services, we'll bring back Analysis Services in a future preview. |
| Arm64 | There's no support for Arm64, and SSMS can't be installed on Arm64 devices. | Run SSMS on a device that isn't Arm64. |
| Connection | If SSMS is configured to open Object Explorer, Query Editor, or Activity Monitor on startup, in **Tools** > **Options** > **Startup**, the connection dialog might appear while SSMS is still loading. | Configure SSMS to open to an empty environment. |
| Installer | The **Product version** listed on the **Details** page within the **Properties** of the bootstrapper `vs_ssms.exe` is incorrect. | There's no current workaround, we'll address this in a future preview. |
| Database Diagrams | Closing a new database diagram before saving generates the error "Object reference not set to an instance of an object. (SqlEditors)". | Save the new database diagram before closing the editor in Database Diagrams. |
| Designers | Closing the view editor before saving in the View Designer generates the error "Object reference not set to an instance of an object. (SqlEditors)". | Save the new view before closing the editor in the View Designer. |
| Integration Services | There's currently no support for Integration Services in [!INCLUDE [ssms-21-md](../includes/ssms-21-md.md)]. | Use SSMS 20.2 to connect to Integration Services, we'll bring back Integration Services in a future preview. |
| License | The "Microsoft Software License Terms" link in the Visual Studio Install splash screen doesn't access a valid URL. | Access the license for SSMS 21 from the "license" link within the Visual Studio Installer, available when customizing the SSMS 21 installation. |
| Maintenance Plans | There's currently no support for creating or editing maintenance plans in [!INCLUDE [ssms-21-md](../includes/ssms-21-md.md)]. | Use SSMS 20.2 to create or edit maintenance plans, we'll bring back Integration Services in a future preview. |
| Menu | Opening a folder from **File** > **Recent Projects and Solutions** generates one of the following errors: "System.InvalidOperationException: Can't enque project dependencies calculation before starting solution load" or "An exception of type NullReferenceException has been encountered." if opening the folder also opens one or more files that were open in the editor when the folder was last closed. | After closing the error, work can continue. Alternatively, close all files in the editor before closing a folder. |
| Menu | Opening a folder from **File** > **Recent Projects and Solutions** generates one of the following errors: "System.InvalidOperationException: Can't enque project dependencies calculation before starting solution load" or "An exception of type NullReferenceException has been encountered." if opening the folder also opens one or more files that were open in the editor when the folder was last closed. | Closing the error allows work to continue. Alternatively, close all files in the editor before closing a folder. |
| Menu | The **File** > **Add** > **New Project or Existing Project** menu option isn't available. | Use SSMS 20.2 to create a new project or open an existing one. |
| Menu | The **File** > **File** menu option isn't available. | Use **File** > **New Query with current connection** or the New Query button to open a new query editor. |
| Menu | The **File** > **Open** > **Project/Solution** menu option isn't available. | Use SSMS 20.2 to open an existing one. |
| Object Explorer | Selecting "Filter" in Object Explorer for any object causes the error "Could not load file or assembly 'Microsoft.DataWarehouse, Version=16.2.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system can't find the file specified. | Use SSMS 20.2 to filter. |
| Options | Enabling Per Monitor Awareness (PMA) by checking **Optimize rendering for screens with different pixel densities (requires restart)** within **Tools** > **Options** can cause issues with dialogs not rendering. | Do not enable **Optimize rendering for screens with different pixel densities (requires restart)** within **Tools** > **Options**. |
| Options | Enabling the Preview options experience (from **Tools** > **Options Experience (requires restart)** > **Preview**) introduces unexpected dialogs and options that SSMS 21 does not currently support. | Do not enable the Preview options experience. |
| Query Editor | Within the query editor in SSMS 21, there's a new file health indicator in the bottom left of the toolbar, which displays errors and warnings. The errors and warnings aren't intuitive for SQL users. | To remove the indicator, go to **Tools**> **Options** > **Text Editor** and uncheck **Show file health indicator**. |
| Results Grid | Tabs and script splitter bar aren't themed. | These will be properly themed in the next preview. |
| Menu | The **File** > **Open** > **Project/Solution** menu option isn't available. | Use SSMS 20.2 to open an existing project or solution. |
| Options | Enabling Per Monitor Awareness (PMA) by checking **Optimize rendering for screens with different pixel densities (requires restart)** within **Tools** > **Options** can cause issues with dialogs not rendering. | Don't enable **Optimize rendering for screens with different pixel densities (requires restart)** within **Tools** > **Options**. |

## Related content

Expand Down
Loading

0 comments on commit 280e69f

Please sign in to comment.