Administrator Guide

9.8.3
- 9.9.4
- 9.9.3
- 9.9.2
- 9.9.1
- 9.9
- 9.8.4
- 9.8.2
- 9.8.1
- 9.8.0

Back Next

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.