Why can Toad sometimes seem to run slower on Oracle 10g?
The short answer is that this is an Oracle 10g DBA best practices issue – and not a Toad problem per se. Toad just happens to expose the symptons since it makes such frequent access to the data dictionary. Oracle versions prior to 10g offered two optimizers: cost and rule – with rule being the default. And very importantly, regardless of which optimizer your database applications used – Oracle internally was using the rule based optimizer for all data dictionary access. Now when using a tool like Toad where we shield users from knowing lots of data dictionary views – we hide that all behind our GUI. But Toad makes numerous SELECT’s against the data dictionary – so this issue is more noticeable in Toad than many other applications. Now that does not mean it’s a Toad bug, but simply Toad has exposed an important performance issue that needs addressed for optimal performance of all your database apps. With Oracle 10g, now data dictionary queries (and in fact all non-hinted queries) explic