VW_DATASET_EVENT_HISTORY

Overview

VW_DATASET_EVENT_HISTORY provides an audit log of all significant events in your Validatar environment — test creations, job executions, metadata refreshes, permission changes, profiling completions, and more. Each row represents one event with its timestamp, triggering user, category, and contextual details.

Use this view for compliance auditing, activity monitoring, and understanding who changed what and when.

Event Type Count: Validatar defines 227 event types across 6 categories. The complete reference is provided below — note that only events that have actually occurred in your environment will appear in this view.

Schema

Event Categories

Validatar defines 227 event types across 6 categories. Not all event types will appear in every environment — only events that have actually occurred are stored. The tables below provide the complete reference.

Authentication (CATEGORY_ID: 441)

Login and session events. Context: Global.

Global Configuration (CATEGORY_ID: 315)

System-wide configuration changes. Context: Global.

Projects & Data Sources

Users & Groups

User Tokens

SSO Providers & User Identities

Lineage Metadata Sources

Data Profiles & Database Engines

Custom Fields & Configuration

Optional Features

Data Processing Engines

Data Source Template Configuration

Data Agents

Quick Start Templates

Data Source Configuration (CATEGORY_ID: 317)

Data source-level configuration changes. Context: Data Source.

Connection & Queries

Comments

Profile Sets & Custom Profiles

Custom Metadata Sources

Metadata (CATEGORY_ID: 316)

Schema metadata changes, profiling activity, and trust score configuration. Context: Data Source.

Schema Events

Table Events

Column Events

Data Source Custom Fields & Ingestion

Profiling

Trust Score Events

Projects (CATEGORY_ID: 314)

Test, job, and folder management within projects. Context: Project.

Test Events

Template Test Events

Job Events

Folder Events

Label Events

Project Configuration Events

User Value Experience (CATEGORY_ID: 611)

Tracks key user engagement milestones. Context varies by event.

Context Types and Security Implications

The CONTEXT_TYPE determines how the event is filtered in the secure view (VW_SECURE_DATASET_EVENT_HISTORY):

Relationships

VW_DATASET_EVENT_HISTORY
    │
    ├── CONTEXT_ID → VW_DATASET_JOBS.PROJECT_ID (when CONTEXT_TYPE = 'Project')
    ├── OBJECT_ID → VW_DATASET_TESTS.TEST_ID (when OBJECT_TYPE = 'Test')
    └── OBJECT_ID → VW_DATASET_JOBS.JOB_ID (when OBJECT_TYPE = 'Job')

Example Queries

Recent Events by User

SELECT
    DATE_CREATED,
    CATEGORY,
    EVENT_NAME,
    OBJECT_TYPE,
    OBJECT_NAME,
    CONTEXT_NAME
FROM REPOSITORY.VW_DATASET_EVENT_HISTORY
WHERE CREATED_BY = 'John Smith'
    AND DATE_CREATED >= DATEADD(day, -7, CURRENT_DATE)
ORDER BY DATE_CREATED DESC;

Project Activity (Tests, Jobs, Folders)

SELECT
    DATE_CREATED,
    CREATED_BY,
    EVENT_NAME,
    OBJECT_NAME,
    CONTEXT_NAME
FROM REPOSITORY.VW_DATASET_EVENT_HISTORY
WHERE CATEGORY = 'Projects'
    AND DATE_CREATED >= DATEADD(day, -1, CURRENT_DATE)
ORDER BY DATE_CREATED DESC;

Metadata Changes (Schema Refreshes, Profiling, Table/Column Changes)

SELECT
    DATE_CREATED,
    CREATED_BY,
    EVENT_NAME,
    OBJECT_NAME,
    CONTEXT_NAME AS DATA_SOURCE
FROM REPOSITORY.VW_DATASET_EVENT_HISTORY
WHERE CATEGORY = 'Metadata'
    AND DATE_CREATED >= DATEADD(day, -7, CURRENT_DATE)
ORDER BY DATE_CREATED DESC;

Automated vs Manual Activity Summary

SELECT
    DATE_CREATED::DATE AS EVENT_DATE,
    CATEGORY,
    SUM(CASE WHEN AUTOMATED = TRUE THEN 1 ELSE 0 END) AS AUTOMATED_COUNT,
    SUM(CASE WHEN AUTOMATED = FALSE THEN 1 ELSE 0 END) AS MANUAL_COUNT
FROM REPOSITORY.VW_DATASET_EVENT_HISTORY
WHERE DATE_CREATED >= DATEADD(day, -30, CURRENT_DATE)
GROUP BY DATE_CREATED::DATE, CATEGORY
ORDER BY EVENT_DATE DESC, CATEGORY;

Permission and Configuration Audit

SELECT
    DATE_CREATED,
    CREATED_BY,
    EVENT_NAME,
    OBJECT_NAME,
    CONTEXT_NAME,
    EVENT_DATA
FROM REPOSITORY.VW_DATASET_EVENT_HISTORY
WHERE EVENT_NAME IN (
    'Data Source Permissions Updated',
    'Project Permissions Updated',
    'Project Data Sources Updated',
    'User Created',
    'User Archived',
    'User Group Updated'
)
ORDER BY DATE_CREATED DESC
LIMIT 100;

Test Status Change History

SELECT
    DATE_CREATED,
    OBJECT_NAME AS TEST_NAME,
    CONTEXT_NAME AS PROJECT_NAME,
    EVENT_DATA
FROM REPOSITORY.VW_DATASET_EVENT_HISTORY
WHERE EVENT_NAME = 'Test Overall Result Status Changed'
    AND DATE_CREATED >= DATEADD(day, -7, CURRENT_DATE)
ORDER BY DATE_CREATED DESC;

Failed Metadata Ingestions and Profile Executions

SELECT
    DATE_CREATED,
    EVENT_NAME,
    OBJECT_NAME,
    CONTEXT_NAME AS DATA_SOURCE,
    EVENT_DATA
FROM REPOSITORY.VW_DATASET_EVENT_HISTORY
WHERE EVENT_NAME IN (
    'Data Source Schema Metadata Ingestion Failed',
    'Profile Set Execution Failed'
)
ORDER BY DATE_CREATED DESC;

Databricks Notes

• Replace DATEADD(day, -7, CURRENT_DATE) with DATE_ADD(CURRENT_DATE(), -7)
• Replace DATE_CREATED::DATE with CAST(DATE_CREATED AS DATE)
• The AUTOMATED column is a boolean — use = TRUE or = FALSE in both engines