> For the complete documentation index, see [llms.txt](https://docs.sprinkledata.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinkledata.com/product/ingesting-your-data/pipelines/databases/features/quality-check.md).

# Quality Check

## Data Quality Rules

### Overview

The Data Quality Rules feature helps ensure data consistency and reliability across database pipelines by validating source and destination data during pipeline execution.

Users can configure automated quality checks, define acceptable variance thresholds, schedule validations, receive notifications, and review execution history.

### Navigation

Navigate to:

Database Pipeline → Pipeline Configuration → Quality Rules

The Quality Rules tab allows users to:

* Configure data quality checks
* Define thresholds
* Schedule executions
* Configure notifications
* View execution history
* Enable or disable rules

<figure><img src="/files/FBqwRbBAyFmGpiQyFuDK" alt=""><figcaption></figcaption></figure>

### Features

#### 1. Row Count Difference Validation

The system compares row counts between source and destination datasets and displays:

* Source row count
* Destination row count
* Difference count
* Variance percentage

&#x20;This helps identify missing or inconsistent data during pipeline execution.

<figure><img src="/files/MWfxDsYiOinElDp3GDHb" alt=""><figcaption></figcaption></figure>

#### 2. Threshold Configuration

Users can define acceptable variance limits between source and destination data.

Supported threshold types:

* Percentage-Based Threshold (Default: 10%)
* Absolute Value Threshold

If the variance exceeds the configured threshold, the quality check is marked as failed.

<figure><img src="/files/FvD0Sd50OjZdiy5IxF8k" alt=""><figcaption></figcaption></figure>

#### 3. Scheduling and Notifications

Quality checks can be:

* Executed manually
* Scheduled at predefined intervals

Email notifications are triggered when:

* A scheduled quality check executes
* A mismatch exceeds the configured threshold

Multiple recipient email addresses can be configured from the Settings panel.

&#x20;

<figure><img src="/files/LWee00WdMsRH7Mc3bHEb" alt=""><figcaption></figcaption></figure>

#### 4. History and Audit Tracking

All quality check executions are stored in the History section.&#x20;

The History page provides:

* Execution details
* Comparison statistics
* Validation results
* Failure messages
* Schema comparison details

Access History from:

&#x20;Quality Rules → Actions → History

<figure><img src="/files/GLaInCMUaF8mDZpPnZCG" alt=""><figcaption></figcaption></figure>

#### 5. Enable or Disable Quality Checks

&#x20;Users can enable or disable quality checks at any time from the Quality Rules section based on operational requirements.

<figure><img src="/files/AvGikuwNqO1CdRcNz2r5" alt=""><figcaption></figcaption></figure>

### Summary:

The Data Quality Rules feature provides automated validation, configurable thresholds, scheduled monitoring, notifications, and historical tracking to help maintain reliable and consistent data across database pipelines.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinkledata.com/product/ingesting-your-data/pipelines/databases/features/quality-check.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
