Data Integrity Suite needs specific permissions to discover your data structures, run quality checks, and store results. Each permission level builds on the previous one, giving the system access to what it needs for that specific task.
For cataloging user-defined schemas
Cataloging discovers and documents your database structure. The Data Integrity Suite reads table definitions, column metadata, and index information to build an accurate data catalog.
- Server Level: CONNECT — allows the system to access the database
- Stored Procedures: EXECUTE on sp_help, sp_helpdb, sp_helptable, sp_helpindex, sp_helpcolumn — retrieves metadata about tables, columns, and indexes
- User Tables: SELECT on all user-defined tables — reads table structure and sample data
For DQ Pipeline Execution
Pipelines run data quality checks across your tables. The system needs to create temporary working tables and execute dynamic SQL queries to analyze your data.
You need all cataloging permissions (above), plus:
- Database Level: CREATE TABLE — creates temporary tables to stage data during quality checks
- Stored Procedures: EXECUTE on sp_executesql — runs dynamic SQL queries for data analysis
For DQ Rules Execution
Rules execution stores quality check results so you can track data issues over time and measure improvement. The system writes results to a dedicated table and may create indexes for faster queries.
You need all pipeline permissions (above), plus:
- Results Storage: INSERT, UPDATE, DELETE on DQ results table — writes and updates quality check results
- Optional: CREATE INDEX — improves query performance on large result sets
Metadata extraction
The import bridge is designed to be read-only and extracts metadata only. As a result, the account used for metadata import requires significantly fewer permissions than accounts used for database administration or data modification.
However, to retrieve advanced metadata such as the SQL definitions of views and stored procedures the import bridge requires read-only access to database system tables. This information is not always exposed through the JDBC driver's standard metadata interfaces. Therefore, assistance from a Database Administrator (DBA) may be required to provision a user account with the necessary permissions.
Permission Guidelines
Because permission requirements vary across database platforms and versions, there is no universal minimum permission set for this import bridge.
To validate connectivity and metadata extraction:
-
Configure the import bridge using a full system administrator account (or an account with equivalent privileges).
-
Verify that metadata import completes successfully.
-
Work with the DBA to create a least-privileged, read-only account that still provides access to the required metadata.
-
Re-test the import bridge using the reduced-permission account to ensure successful metadata extraction.
Sybase ASE: No specific permission requirements are documented for Sybase ASE. Permission needs may vary depending on the database configuration and version. It is recommended to follow the validation process described above.