Database Discovery Task Wizard - Table Filtering
Use the Table Filtering page of the database discovery wizard to determine which tables to scan.
Steps
- Use Include tables to enter the user names, schemas, or table names to scan, separated by semicolons.
- The discovery filtering mechanism uses a specific full path search pattern. The search pattern is matched as follows: [Catalog.Schema.Table]
- Use an asterisk (*) before the Database entry type, i.e. *.TB_123, only if the ending of the full path ends with.TB_123. For instance: MyDB.Sys.TB_123.
- Use an asterisk (*) before and after the Database entry type, i.e. *.Sys.*, for entries that may have entries before and after it in the full path. For instance: MyDB.Sys.TB_123.
In order for tables to be detected within the full path, use the structure described above.
-
- Database discovery analyzes data in 5000-record chunks. Each chunk is treated independently, and all policy thresholds are validated against a single chunk. No aggregation of analysis results is accumulated over the entire table. Therefore, if a policy keyword has a threshold of 10 and this keyword is detected 3 times in each of 5 chunks, no breach is triggered. Column names are included in each chunk that is analyzed. Only column names containing fewer than 40 characters are supported.
- The discovery filtering mechanism uses a specific full path search pattern. The search pattern is matched as follows: [Catalog.Schema.Table]
- Use Except to enter the user names, schemas, or table names not to scan.
- Click Next, then continue with Emailing discovery task status reports.