How can we help you today?

Improve schema handling in SQL Server DB profile

a

anonymous

started a topic
almost 10 years ago

[This topic is migrated from our old forums. The original author name has been removed]

The sqlserver DB profile has poor support for schemas in the DB tree browser.
First of all, the option "Show only default Database/Schema" does not seem to work at all (IMO a bug).
Secondly, there's no schema tree node. Instead, all tables are attached directly to the main "Tables" node. This flat approach may quickly lead to thousands of tables. In an environment where each user has its own schema, this becomes almost unusable. On the positive side of things, tables are at least grouped by schema. (and not by table name as done by Aqua Data Studio)
Since there's no schema node, there's also no way to filter this list. Especially because the schema qualifier is not being taken into account when table names are filtered (inconsistency, the schema should either have its own node or it should be considered part of the name)
Current workaround:
- Use the generic DB profile. Features are lost (triggers etc.) and some stuff doesn't work (foreign keys, reference graph etc.)
- Use DB Visualizer Free
Proposed short-term solution: Let table name filter apply to the whole name including the schema qualifier.
Long-term: A schema tree as other DB profiles and the free version have it would be very nice.

1 Comment

Roger Bjärevall

said
almost 10 years ago

[This reply is migrated from our old forums.] [Attachment has been removed.]

Re: Improve schema handling in SQL Server DB profile

Bach,
> {quote:title=bach wrote:}{quote}
> The sqlserver DB profile has poor support for schemas in the DB tree browser.
>
> First of all, the option "Show only default Database/Schema" does not seem to work at all (IMO a bug).
Just tried and I get only the default Database listed in the objects tree.
(See attached image).
> Secondly, there's no schema tree node. Instead, all tables are attached directly to the main "Tables" node. This flat approach may quickly lead to thousands of tables. In an environment where each user has its own schema, this becomes almost unusable. On the positive side of things, tables are at least grouped by schema. (and not by table name as done by Aqua Data Studio)
DbVisualizer Personal present the objects in the same was as "Microsoft SQL Server Management Studio Express" does.
> Since there's no schema node, there's also no way to filter this list. Especially because the schema qualifier is not being taken into account when table names are filtered (inconsistency, the schema should either have its own node or it should be considered part of the name)
We'll check at the problem filtering compound object names (Ex: schema.table).
> Current workaround:
> - Use the generic DB profile. Features are lost (triggers etc.) and some stuff doesn't work (foreign keys, reference graph etc.)
> - Use DB Visualizer Free
If you have a license, you never need to uninstall it and run DbVisualizer Free. The recommended solution to get the Free appearance of database objects is to switch to the "generic" database profile.
> Proposed short-term solution: Let table name filter apply to the whole name including the schema qualifier.
We'll look into it.
> Long-term: A schema tree as other DB profiles and the free version have it would be very nice.
The SQL Server database profile in DbVisualizer tries to mimic the SQL Studio Server Express Management (...) from Microsoft (and former SQL Server Analyzer).
It is a rather easy fix to introduce a Schema level in the tree. However, I don't know if this is what the majority of users want.
Best Regards
Roger