Skip to main content

SQL Development Policies and Approval Processes

NineData provides SQL development policies and approval processes to standardize collaborative development and control database-change risk. SQL development policies pre-check SQL statements. Approval processes determine whether a task can be submitted, requires manual approval, and which approval nodes handle it based on the pre-check result and task type.

How policies and processes work​

When you create a data source in NineData, specify an environment for the data source. By default, NineData provides Production and Development environments with an SQL development policy and an approval process group associated with each environment. Data sources in the environment use the corresponding policy and process configuration.

Create or customize development policies and approval process groups, and then associate them with an environment, data source, or database group.

  • Environment association: SQL development policies and approval process groups apply to all data sources in the environment.

    tip

    If a data source has its own SQL development policy or approval process group, that data source uses its own configuration. Other data sources in the same environment are not affected.

  • Data source association: The selected SQL development policy and approval process group apply directly to the data source and override the inherited environment configuration.

  • Database group association: A database group can use its own SQL development policy and approval process group for unified changes across distributed databases.

SQL development policies define pre-check rules. When a user runs SQL or submits a governed task, NineData checks it against the associated policy. A compliant operation can continue. When a rule requires improvement, NineData uses the approval process group to determine whether to block the operation or guide the user to submit an approval task.

Approval process groups organize approval processes for the same scope. Professional Edition, including Community Edition, has one default approval process template in each group, which can be adjusted as needed. Enterprise Edition can add multiple condition-based processes, manage approval process templates, and change process priority.

Approval processes define the handling of a task after it matches conditions, including whether submission is allowed, whether manual approval is enabled, and which approval nodes are used. If multiple Enterprise Edition processes match, NineData selects the highest-priority process according to the configured order.

Approval process templates belong to an approval process group and centrally maintain approval-node configurations for reuse across approval processes. Editing a template also updates the processes that reference it.

Modules​

  • Environment configuration: Associate one SQL development policy and one approval process group with an environment. The configuration applies to data sources in the environment.
  • Data source configuration: Associate one SQL development policy and one approval process group with a data source. The data source configuration has higher priority than the environment configuration.
  • Database group configuration: Associate an SQL development policy and approval process group with a database group. This configuration overrides the inherited environment configuration for that group.
  • SQL development policy: Configure rules for schema changes, SQL queries, updates, and other controlled operations.
  • Approval process group: Organize approval processes and approval process templates by task type.
  • Approval process: Configure whether a task can be submitted, whether manual approval is required, and which approvers handle it.
  • Approval process template: Reuse approval-node configurations so that the same nodes do not need to be maintained in multiple processes.

Edition differences​

  • Professional Edition, including Community Edition: Each approval process group has one default approval process template. NineData does not initialize 24 child processes; administrators can edit the default template.
  • Enterprise Edition: In addition to the default template, add multi-condition approval processes, manage approval process templates, and change the priority order of processes.

Together, policies and processes reduce non-compliant changes and make database development safer and more auditable.

Next steps​