Allow me to specify schemas to include or exclude
The options to "Only load suggestions for certain databases" and "Don;t load suggestions for certain databases" are nice, but it'd be really useful to also be able to include or exclude on a per schema basis.
We added schema filtering in SQLPrompt 9.4.15. You can learn more about the feature here: https://documentation.red-gate.com/sp9/managing-sql-prompt-behavior/managing-connections-and-memory
We would love to hear your feedback.
I've tried this now for several days and while I echo my earlier feedback. When I do decide to query a table in an excluded schema, it would be nice to be able to pull in those columns.
So perhaps this feature works more like "Exclude from suggestions, until desired" rather than "exclude it completely"
I would add to this suggestion some mechanics: Exclusions should be able to be temporarily ignored.
Example: let's say I have a schema called "audit", that I exclude from my default list of suggestions.
However I write a query where I DO want to pull in a table inside of that schema.
I type in SELECT * FROM audit.
I would expect at this point to see all suggestions from that schema.
Or, to be a little more intelligent, if I'm typing in a table name that lives in an exclude schema, perhaps if I run out of results from included schemas, maybe you highlight the result and say "this lives in the 'audit' schema which is excluded, is this what you meant?" (or something more intelligent).
Will all the great options that SQL Prompt has, it seems strange that this one isn't one of them.
Could we include/exclude schemas based on wild card characters?
Anders Ebro (TheSmileyCoder) commented
Most of our tables have a history table for logging purposes, using the same name, but a schema named "hist". I almost never design sql against the hist tables, and it would really be helpful if I could exlcude that entire schema from showing up in the suggestion list.
In about half of our databases, we have hundreds of schemas all with the same structure. SQL prompt is unusable for those dbs for 3 reasons. The suggestions dropdown is very slow, having to choose schema everytime to filter the list is slow again, and we also hit the memory limit as well.
It would be useful to have the schema(s) filter on a per tab temporary basis, as we change the schema we are looking at reasonably often.
Harish Supe commented
Second to Timothy. I have exact same problem with the conflict tables and I landed on this page searching solution for it.
We are coming from SAAS based company and we have our client segregated based on Schema's rather than DB's. When we have too many schema in a DB the load fails and Prompt becomes use less. Having a functionality to choose specific schema would be very useful.
Garrett Geier commented
I agree with Timothy. I'm all for this suggestion if certain objects can be excluded.
Timothy Eichman commented
SImilarly, being able to exclude "conflict" tables from the object list would be very helpful... it isn't bad if your table is before "conflict", but annoying when its after it...
Since they are "dbo" schema tables, adding a scheme filter specifically won't help my my issue, but if you're in there adding filtering, see if you can take it one more level to allow users to filter tables matching a string filter (e.g. "conflict%").
Martin Knight commented
Excluding particular schema's from the SQL Prompt suggestion list would be a very nice feature and would definitely improve workflow.