SQL Server Management Studio (SSMS) is a powerful tool that allows users to manage and interact with SQL Server databases. However, with its extensive range of settings, it can sometimes be overwhelming for users to navigate and configure the tool to their specific needs.

In a recent email from one of my clients, they expressed concern about a strange behavior they were experiencing in SSMS. When connecting to their SQL Server 2016 instance using SSMS 2014, they were unable to see system views and objects. This discrepancy caused confusion and raised questions about the integrity of their installation.

After investigating the issue, I discovered that the problem was not with the installation itself, but rather a specific setting within SSMS. The setting in question can be found under Tools > Options > Environment > Startup. It is called “Hide system objects in Object Explorer.”

This setting, when enabled, hides system objects such as system views, tables, and stored procedures in the Object Explorer. It is designed to reduce clutter and improve the user experience by only displaying user-created objects. However, it can also lead to confusion if users are not aware of its existence.

In the case of my client, one of their developers had enabled this setting in SSMS 2016 to avoid clutter in the Object Explorer. As a result, when connecting to the same instance using SSMS 2014, the system objects were not visible.

If you have encountered a similar issue where system objects are not visible in SSMS, I recommend checking the “Hide system objects in Object Explorer” setting. Ensure that it is disabled if you want to see all objects, including system objects, in the Object Explorer.

It is important to note that this setting is specific to each version of SSMS. Therefore, if you have multiple versions installed on your machine, you may need to adjust the setting individually for each version.

Understanding and configuring the various settings in SSMS is crucial for efficient database management. By familiarizing yourself with the available options and their impact, you can tailor SSMS to suit your specific needs and enhance your productivity.

Have you encountered any other settings in SSMS that have caused confusion or unexpected behavior? Share your experiences in the comments below!