Major KNOWN Issue --- Stop requiring product to login to all databases on server
The product requires you to have at least read access to all databases on provided server... because when the product opens... and db access is lacking... then USER is failing login attempts on PRODUCTION SERVERS to which user has no access. This creates GREAT FRUSTRATION for DBA and AUDITing groups.
Tom
shared this idea
-
iokevins
commented
I'm uninstalling SQL Search until this gets resolved
-
Chris Suire commented
Not sure if this is the same issue or not, but I want to stop SQL Search from searching all databases automatically. When it tries to search hundreds of databases it causes the program to freeze up. I'd rather it not default to all databases...
-
Jacob
commented
This should be trivial to fix: whatever SQL query SQL Search is emitting to enumerate databases on an instance just needs to have a condition added to its WHERE clause to check whether the current user has access to a given DB, eg:
...WHERE has_dbaccess(name) = 1
or similar.
-
Anonymous
commented
We have logon triggers on our SQL servers and when the user doesnt have access to certain databases, we get alerts out from every database they dont have access to. I raised this as a support ticket 117319 and was told it was not a bug but a feature request. SQL search has the same bug as SSMS 2016 RTM, where the Object Explorer tries to do the same thing, when connecting to earlier versions of SQL server