Table of Contents

Search

  1. Preface
  2. Introduction to Dynamic Data Masking Administration
  3. Authentication
  4. Security
  5. Connection Management
  6. JDBC Client Configuration
  7. ODBC Client Configuration
  8. Access Control
  9. Logs
  10. High Availability
  11. Server Control
  12. Performance Tuning
  13. Troubleshooting
  14. Appendix A: Database Keywords

Administrator Guide

Administrator Guide

Rule Processing

Rule Processing

Rule processing causes Dynamic Data Masking overhead. Understanding the factors that contribute to rule processing time is necessary in order to increase efficiency.
Dynamic Data Masking processing time varies based on the matcher or action type that you use. The following list describes the performance impact for each rule type:
Rules that access the database
Dynamic Data Masking takes between 10 and 100 milliseconds to access the database and about 100 milliseconds to handle a packet.
The following matchers and actions require Dynamic Data Masking to access the database:
  • PL/SQL Function matcher
  • PL/SQL Function action
  • The Mask action if the statement contains an asterisk in the column list
Rules that require SQL parsing
Dynamic Data takes between one and ten milliseconds to perform SQL parsing, depending on the complexity of the statement.
The following matchers and actions require SQL parsing:
  • From Clause Object matcher
  • SQL Syntax matcher
  • Mask action
  • Replace Table action
Other types of rules
Rules that do not access the database or require SQL parsing take Dynamic Data Masking between 10 and 50 microseconds (0.05 milliseconds) to complete.

0 COMMENTS

We’d like to hear from you!