I’ve seen some people on competing product discussion boards say things like Toad’s schema browser Is far too bloated – with too many tabs and images sucking up all the precious real-estate. But like anything else in Toad, if you don’t experiment with and utilize all the cool options it offers – you could very easily arrive at this quite mistaken conclusion. So now let’s examine just how one configures the schema browser for their specific or specialized needs. It’s so easy – you’ll probably feel like doing your Homer Simpson “doh” impression.

 

Let’s start with the default schema browser in all it’s glory – thus with all the possible tabs, and furthermore with the icon images turned on as shown below. And I fully agree, Toad setup this way is too crowded. But we can configure the schema browser to appear however we prefer by simply clicking on the schema browser window’s toolbox icon, pointed to by the arrow in this screen snapshot, which facilitates adjusting all the schema browser display options.

 

 

When we open this configuration drop-down box – we get the following simple choices show here for adjusting the major schema browser’s display behavioral characteristics.

 

 

I’m going to keep the multi-line tabbed style (my personal favorite), but I am going to turn off the Left Hand Side (LHS) images and hints. Did you notice that Toad can do a tree-view just like Quest’s SQL Navigator and Oracle’s SQL Developer? So if you ever wondered if Toad has feature 'X', the base answer is yes – look to Toad’s many options. 

 

Now I’m going to open the Configure LHS Object Types screen – which permits you to turn on/off the various object types displayed, rearrange their order, and define their own personalized captions for those objects. Here’s an expanded view of this screen.

 

 

Let’s assume that we’re setting Toad up for use by a developer.  We may not need to display many of the choices since they may not really apply to the developer job function. Thus one might choose to turn off superfluous objects, shorten the remaining captions to further conserve space, and arrange their order to suite taste. Here’s the result for what I chose. Wow – I got back down to just two lines. Did you notice that original screen snapshot had room to display just 16 tables on the LHS, whereas my new configuration has room to display 29? There’s very little wasted real-estate space now. I just had to do my homework to get it the way I liked.

 

 

Finally, what if you’re a DBA – how would one best configure the schema browser? The answer is actually quite simple – the same as for the developer, and then use the database browser as a front-end to the schema browser as shown below. Now we have an easy way to navigate both schema and database level objects via one single and simple interface. Yet we’ve retained the famous Toad tabbed look and feel – while not wasting any space.