Hello Harry,
Thank you for posting question on Microsoft Windows Forum!
Well! The fact of the matter is that the filtering options in SQL Server Management Studio (SSMS) Object Explorer are quite limited. Currently, the built-in filters only support Equals, Contains, and Does Not Contain for object names, plus a few basic property filters (like schema or creation date). There is not a way to apply more advanced conditions (like regex, starts with, ends with, multiple criteria combined with AND/OR) directly in Object Explorer.
However, there are some workarounds you can consider to make managing large object lists significantly less painful.
- SSMS includes a secondary interface designed precisely for handling large sets of metadata. If you click on a folder in Object Explorer (such as Tables or Stored Procedures) and press F7 (or go to View > Object Explorer Details), it opens a tabular, search-friendly pane. While it still relies on the basic operators, this pane is highly superior for large databases. There is a real-time search box at the top right of the Details pane. Unlike the standard Object Explorer tree view, you can multi-select, delete, or script out dozens of objects at once. For the performance, it handles rendering large lists much faster than the visual tree view. For more information https://learn.microsoft.com/en-us/ssms/object/manage-objects-by-using-object-explorer
- If your pain stems from scrolling past thousands of tables to find things, a recent feature addition (added in SSMS 20+ / 21) allows you to Group Objects by Schema natively. You can go to Tools > Options. Navigate to SQL Server Object Explorer > General. Check the box to Group objects by Schema. This collapses the massive flat lists of tables/procedures into folder structures based on their Schema, dramatically reducing the amount of visual noise. For more information https://learn.microsoft.com/en-us/ssms/object/open-and-configure-object-explorer
Regarding feature request, submitting feedback via the SQL Server Feedback Portal or SSMS Developer Community might be the best way to request this feature. Since Microsoft does act on community feedback, especially for SSMS usability improvements.
Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same query too.