Rules tagged with: Performance

Efficient use of resources.

• G-1240Try to index foreign key columns.

  Reliability
• G-2135Avoid assigning values to local variables that are not used by a subsequent statement.

  Reliability
• G-2210Avoid declaring NUMBER variables, constants or subtypes with no precision.

  Reliability
• G-2220Try to use PLS_INTEGER instead of NUMBER for arithmetic operations with integer values.

  Reliability
• G-2230Try to use SIMPLE_INTEGER datatype when appropriate.

  Reliability
• G-3145Avoid using SELECT * directly from a table or view.

  Reliability
• G-3210Always use BULK OPERATIONS (BULK COLLECT, FORALL) whenever you have to execute a DML statement for more than 4 times.

  Reliability
• G-3310Never commit within a cursor loop.

  Reliability
• G-4130Always close locally opened cursors.

  Reliability
• G-4230Always use a COALESCE instead of a NVL command, if parameter 2 of the NVL function is a function call or a SELECT statement.

  Reliability
• G-4240Always use a CASE instead of a NVL2 command if parameter 2 or 3 of NVL2 is either a function call or a SELECT statement.

  Reliability
• G-4360Always use a WHILE loop to process a loose array.

  Reliability
• G-4390Avoid use of unreferenced FOR loop indexes.

  Reliability
• G-7160Always explicitly state parameter mode.

  Reliability
• G-7170Avoid using an IN OUT parameter as IN or OUT only.

  Reliability
• G-7210Try to keep your packages small. Include only few procedures and functions that are used in the same context.

  Reliability
• G-7250Never use RETURN in package initialization block.

  Reliability
• G-7460Try to define your packaged/standalone function deterministic if appropriate.

  Reliability
• G-7730Avoid multiple DML events per trigger.

  Reliability
• G-7740Never handle multiple DML events per trigger if primary key is assigned in trigger.

  Reliability
• G-7810Never use SQL inside PL/SQL to read sequence numbers (or SYSDATE).

  Reliability
• G-8110Never use SELECT COUNT(*) if you are only interested in the existence of a row.

  Reliability
• G-8120Never check existence of a row to decide whether to create it or not.

  Reliability
• G-8510Always use dbms_application_info to track program process transiently.

  Reliability

24 total