Find in Object Explorer not working
Posted: Mon 08 Oct 2018 16:24
I'm having the same problem that was reported last November. Even though SQL Search finds the object in the search window, the "Find in Object Explorer" window only opens the database list, but nothing more.
I've tried it on a couple of different SQL Servers and it works on some of them but not on others. The one thing I've found in common is that is does NOT work on databases that are part of a High Availability Group. Those databases are displayed slightly differently in Object Explorer that a regular database. I'm wondering if SQL Search is doing some kind of an exact string match.
For a regular database, say "AdventureWorks", the name displayed in Object Explorer is "AdventureWorks". Here's a simple example:
However, if the AdventureWorks database is part of an availability group, the name displayed in Object Explorer is "AdventureWorks (Synchronized)" -- where the "Synchronized" is an indicator that this database is being sync'd with another server for high availability:
Is there a log or something I could send to help track this issue? Or could dbForge confirm that they are traversing the Object Explorer tree looking for an exact match on database name?
Thanks.
I've tried it on a couple of different SQL Servers and it works on some of them but not on others. The one thing I've found in common is that is does NOT work on databases that are part of a High Availability Group. Those databases are displayed slightly differently in Object Explorer that a regular database. I'm wondering if SQL Search is doing some kind of an exact string match.
For a regular database, say "AdventureWorks", the name displayed in Object Explorer is "AdventureWorks". Here's a simple example:
However, if the AdventureWorks database is part of an availability group, the name displayed in Object Explorer is "AdventureWorks (Synchronized)" -- where the "Synchronized" is an indicator that this database is being sync'd with another server for high availability:
Is there a log or something I could send to help track this issue? Or could dbForge confirm that they are traversing the Object Explorer tree looking for an exact match on database name?
Thanks.