Comments
Sort by recent activity
SSMS 19.1.56.0 SQL Search 3.6.3.3612 Several on our team are also experiencing this same issue Its very disruptive to our workflow. Our environment consists of around 30 separate databases with mostly identical schemas and object names. These database also have custom elements and share data workflows with application databases on linked SQL database servers. Typical use case for us involves using SQL Search on a select single database by making selections from the "Server" and "Database" dropdown options inside the SQL Search menu. We then use the succinct list of relevant objects making it easier for us to spot custom or atypical objects for review and discovery. This process is derailed because Search will now update the "database" and "Server" dropdown options automatically to match whatever Server and Database you have selected in the Object explorer. When search defaults back to "all databases" our results go from from 10 to 300+ as an example. Also, since search results are no longer persistent and always change depending on what object you last clicked on in Object Explorer, it makes it functionally impossible to inspect search results that were purposely applied to more than one database. As soon as you double click on a line in the search results SSMS will navigate you to that object in Object Explorer and the search results will be discarded to only show the results for the database of that object you are currently inspecting. If you are connected to more than one SQL server in the SSMS Object Explorer, Search will take liberty to apply an irrelevant earlier search query for a different server and database on whatever server you happen to be looking at in that moment. / comments
SSMS 19.1.56.0 SQL Search 3.6.3.3612Several on our team are also experiencing this same issue Its very disruptive to our workflow. Our environment consists of around 30 separate databases with most...