SQL Server 2016 has brought about some significant changes, particularly in the realm of SQL Server Management Studio (SSMS). One of the most notable enhancements is the ability to have a different release cycle for SSMS, with updates being rolled out almost every month. In this article, we will delve into the exciting world of SSMS enhancements.

As a SQL Server professional, I often visit customer locations and observe the various challenges faced by DBAs while working on their servers. During a recent conversation, I encountered a customer who had a staggering 86 databases on their server. Navigating through such a large number of databases was a daunting task, especially since SSMS lacked the ability to filter the list. However, with the latest release of SSMS, I discovered that this functionality has been added to the toolset.

To simulate this new capability, simply navigate to the Databases section and click on the “Filter” button. Alternatively, you can right-click and select “Filter” followed by “Filter Settings”. These options will now be enabled at the database node as well. Upon clicking, a familiar screen will appear where you can enter the values to filter. Once you press the “OK” button, the databases node will be automatically filtered. For example, if you enter “Adventure” in the filter, you will see all the databases with “Adventure” in their name.

Although this may seem like a small addition to the tool, it is a powerful feature that many of us have been longing for. The ability to filter databases based on specific criteria greatly enhances productivity, especially in environments with a large number of databases.

I would love to hear your thoughts on this new feature. Have you had the opportunity to use it in your own environments? What is the maximum number of databases you have encountered on a single server? Please share your experiences and insights in the comments section below.