Explore >> Select a destination
|
You are here 
|
sqlmaria.com | ||
| | | | |
parvu.org
|
|
| | | | | To identify unused PL/SQL code in an Oracle database, several methods are recommended. Strategies include auditing PL/SQL execution, using DBA_DEPENDENCIES views to track dependencies, and analyzing execution data through DBMS_PROFILER. A process for safely removing unused code should be established, including renaming suspected units and ensuring backups before deletion. | |
| | | | |
blog.sqlora.com
|
|
| | | | | One of the most mentioned use cases for table SQL macros is the implementation, which works like a parameterized view. My first post on this is from 2020 and it... | |
| | | | |
www.greenstechnologys.com
|
|
| | | | | Native Dynamic SQL in Oracle | |
| | | | |
dban00b.wordpress.com
|
|
| | | 2016-11-29 EDIT: Oracle has announced that in 12.2 the features that drove this overuse of the result cache (dynamic stats triggered by SPDs) will default to off, and provided patches to apply to 12.1 as well. More info here. Also, some investigation by Mauro Pagano around the impact of the new OPTIMIZER_ADAPTIVE_STATISTICS parameter turned up... | ||
