OraDotNetDev
Member
We have a requirement, as I'm sure many organisations do to carry out Code Search (Impact Analysis) across all schemas and Compare Objects (create Change Scripts.) Our DB is around 1.5 TB with ~250K objects ~9000 are stored code across 100 schemas. the numbers are reduced by a third* if we could exclude system objects.
The code search has always been painfully slow for us taking +/- 2 hours, whilst another well known tool only takes 10 minutes. This is simply unusable and is forcing us to start considering other more expensive tooling. The comparison performance is also a similar experience.
Working with our DBAs and tracing the searches carried out by PL/SQL Developer it appears (though I could be wrong) that there is no use of Binding Variables and every query is being hard parsed, fetched and processed client side rather being parameterised and driven by common cursors using effective join conditions which would let our very powerful Oracle Servers do the heavy lifting.
I've raised this as an issues with support directly before but was told that it wasn't a concern!
Is this not an issue for other users? Is there any chance of this being resolved this year? If not we will probably have to migrate to another tool which would be a pity.
similar thread from 2005
Another poll on this issue
There are some additional enhancements, I think might also help: Excluding objects without any schemas from pick lists. When comparing all objects, the ability to exclude system users, in the object comparison standard functionality such as select all, Select all up/down is broken.
The code search has always been painfully slow for us taking +/- 2 hours, whilst another well known tool only takes 10 minutes. This is simply unusable and is forcing us to start considering other more expensive tooling. The comparison performance is also a similar experience.
Working with our DBAs and tracing the searches carried out by PL/SQL Developer it appears (though I could be wrong) that there is no use of Binding Variables and every query is being hard parsed, fetched and processed client side rather being parameterised and driven by common cursors using effective join conditions which would let our very powerful Oracle Servers do the heavy lifting.
I've raised this as an issues with support directly before but was told that it wasn't a concern!
Is this not an issue for other users? Is there any chance of this being resolved this year? If not we will probably have to migrate to another tool which would be a pity.
similar thread from 2005
Another poll on this issue
There are some additional enhancements, I think might also help: Excluding objects without any schemas from pick lists. When comparing all objects, the ability to exclude system users, in the object comparison standard functionality such as select all, Select all up/down is broken.