Tips for Analyzing PL/SQL Code

How do you deal with PL/SQL code maintenance and code analysis ? An effective code management strategy emphasizes code tracing, profiling, testing and reporting. In this session, Shashank Bark returns to offer best practices and useful techniques to analyze PL/SQL code using various data dictionary views, initialization parameters, and built-in packages.
1. Tracking exceptions in PL/SQL code
2. Tracing and generating reports on PL/SQL source code using DBMS_METADATA package
3. PL/Scope toola
4. Getting the most out of DBMS_UTILITY.FORMAT_CALL_STACK

[@M.Alsharafi]

Awesome👍

[@asrytube]

Wonderful and very informative video. really enjoyed. Thanks for posting such great stuffs for free.

[@BigCorrado]

Thank you :)

[@oracledevs]

No problem 😊

[@userzzzabc]

I din like his approach, making simple things appear complex

[@SumanAmara]

Mind blowing very good video sir keep doing good work and I request how you get this information in what website we need to lean this kind of knowledge and improve this more 👌

[@dr10gdba]

Excellent - where can I find source codes for procedures and functions in videos... appreciated

[@knandi73]

I require the particular things exactly....I don't need "Kind of things".

[@knandi73]

Please avoid unnecessary comments which do not add values to learning rather increases the length of video and wastes time and makes the coaching irritating.... Communication should be very fluent so that you do not need to take help of unnecessary words to make the continuity in speech. Actual knowledge delivery = ~25 mins. Unncecessary talk = ~30 mins

[@knandi73]

It's not good and professional to interrupt the trainer when he delivers....It disturbs the flow, speaker and whole audience. Listen properly till the end, be ready with your questions and ask them at the last.