many files and new folders

Author: Steven Feuerstein

plsql/code-analysis/README.md

@@ -1,7 +1,7 @@
-As a database programming language, PL/SQL code is stored in the Oracle Database. 
-That means that we can analyze our code using data dictionary views, most importantly 
-ALL_IDENTIFIERS and ALL_STATEMENTS, which are populated by PL/Scope.
+As a database programming language, PL/SQL code is stored in the Oracle Database. That means that we can analyze our code using data dictionary views, most importantly the ALL_IDENTIFIERS and ALL_STATEMENTS views, which are populated by PL/Scope.
 
 This folder offers a set of stand-alone queries and procedures that demonstrate PL/Scope and give you a quick and easy way to get started with this fantastic utility.
 
 Philipp Salvisberg has also put together a very nice utility full of packages and views that can take you a long way towards fully leverage PL/Scope. Check it out here:  https://github.com/PhilippSalvisberg/plscope-utils
+
+For a broader roundup of resources related to PL/Scope, check out Steven Feuerstein's blog post here: https://stevenfeuersteinonplsql.blogspot.com/2018/07/the-plscope-resource-center.html

plsql/code-analysis/find-invocations-of-subprogram.sql

@@ -0,0 +1,87 @@
+/*
+When contemplating a change to a subprogram, impact analysis is critical. 
+And the first thing you need to know is: where is the subprogram called? 
+With PL/Scope (11.1), you can now get the definitive answer to that question, 
+regardless of possible re-uses of the same name in different program units, 
+by utilizing the unique signature values stored in ALL/USER_IDENTIFIERS.
+*/
+
+-- Turn on PL/Scope
+ALTER SESSION SET plscope_settings='identifiers:all' ;
+
+-- Who Calls Me? Answered by PL/Scope
+-- I look up the declaration of that subprogram in the package, then search 
+-- for its signature across all other program units compiled with PL/Scope enabled.
+CREATE OR REPLACE PROCEDURE who_calls_me (pkg_in    IN VARCHAR2, 
+                                          prog_in   IN VARCHAR2) 
+IS 
+BEGIN 
+   FOR rec 
+      IN (SELECT srch.object_name, srch.name 
+            FROM user_identifiers srch, user_identifiers src 
+           WHERE     src.object_name = pkg_in 
+                 AND src.object_type = 'PACKAGE' 
+                 AND src.usage = 'DECLARATION' 
+                 AND src.name = prog_in 
+                 AND src.signature = srch.signature 
+                 AND srch.usage = 'CALL') 
+   LOOP 
+      DBMS_OUTPUT.put_line ( 
+         rec.object_name || ' calls ' || pkg_in || '.' || prog_in); 
+   END LOOP; 
+END;
+/
+
+-- Create Some Program Units
+CREATE OR REPLACE PACKAGE my_pkg1 
+IS 
+   PROCEDURE my_proc; 
+END;
+/
+
+CREATE OR REPLACE PACKAGE BODY my_pkg1
+IS
+   PROCEDURE my_proc
+   IS
+   BEGIN
+      NULL;
+   END;
+END;
+/
+
+CREATE OR REPLACE PACKAGE my_pkg2
+IS
+   PROCEDURE my_proc;
+END;
+/
+
+CREATE OR REPLACE PACKAGE BODY my_pkg2
+IS
+   PROCEDURE my_proc
+   IS
+   BEGIN
+      NULL;
+   END;
+END;
+/
+
+CREATE OR REPLACE PROCEDURE my_proc1
+IS
+BEGIN
+   my_pkg1.my_proc;
+END;
+/
+
+CREATE OR REPLACE PROCEDURE my_proc2
+IS
+BEGIN
+   my_pkg2.my_proc;
+END;
+/
+
+-- Check for Usages
+BEGIN 
+   who_calls_me ('MY_PKG1', 'MY_PROC'); 
+END;
+/
+

plsql/code-analysis/find-sql-with-hints.sql

@@ -0,0 +1,55 @@
+/*
+As of 12.2, PL/Scope now analyzes the static SQL statements that 
+appear in your PL/SQL program units. It allows you to answer with ease 
+questions like "Where do I use hints in my SQL statements?" 
+
+Doc: http://docs.oracle.com/database/122/ADFNS/plscope.htm#ADFNS022
+*/
+
+ALTER SESSION SET plscope_settings='identifiers:all, statements:all';
+
+CREATE OR REPLACE PROCEDURE proc1
+IS
+   l_id   INTEGER;
+BEGIN
+   SELECT /*+ result_cache */
+          employee_id
+     INTO l_id
+     FROM hr.employees
+    WHERE last_name = 'KING';
+END;
+/
+
+CREATE OR REPLACE PROCEDURE proc2
+IS
+   TYPE nt IS TABLE OF INTEGER;
+
+   l_ids   nt;
+BEGIN
+   SELECT /*+ FIRST_ROWS(10) */
+          employee_id
+     BULK COLLECT INTO l_ids
+     FROM hr.employees;
+END;
+/
+
+CREATE OR REPLACE PROCEDURE proc3
+IS
+   TYPE nt IS TABLE OF INTEGER;
+
+   l_ids   nt;
+BEGIN
+   SELECT employee_id
+     BULK COLLECT INTO l_ids
+     FROM hr.employees;
+END;
+/
+
+-- Does the statement have a hint?
+-- What could be simpler?
+SELECT object_name, 
+       line, 
+       full_text 
+  FROM user_statements 
+ WHERE has_hint = 'YES';
+