Hide relationship classes, feature datasets, and topo dsets from appearing across all schemas

[ChadMarch1]

Relationship classes, Feature Datasets, and topological datasets are viewable across all schemas of a db and is quite annoying.

I've done research and have found posts complaining about this since as early as 2009:
http://forums.esri.com/Thread.asp?c=158&f=2284&t=279568

and techinical articles posted recently explaining it:
http://support.esri.com/en/knowledgebase/techarticles/detail/22721

But y'all should really do something about this. If tables are contained to their schemas, related elements like RC's, FD's, and topology should all be as well.

[Bud]

@YannickBourone 

Interesting. Although in cases like mine, my connections legitimately include tables from other users. So the "List only objects owned by the connecting user" setting would exclude those tables, which wouldn't be what I'd want.

[DeanMoiler]

@YannickBourone 

Very useful to know is available! I wasn't aware of this capability, thanks for bringing to our attention.  As with @Bud we've got content shared with particular DB users to bring content together (e.g. PORTAL_VIEWER), that are then shared as services. With this option the viewer user ends up with no content, so filtering display of content types would be fantastic for our workflows. Thanks for sharing!