My Hours to Azure Synapse Integration

How Datrise loads My Hours into Azure Synapse

Datrise syncs My Hours's time logs, projects, tasks, clients, team members, and billable rates into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

My Hours: Time tracking and billable hours for projects.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How My Hours entities map to Azure Synapse

My Hours entity	Azure Synapse object	Notes
time logs	`my_hours_time_logs`	id PK · custom fields → NVARCHAR(MAX) JSON columns
projects	`my_hours_projects`	id PK · linked to my_hours_time_logs
tasks	`my_hours_tasks`	id PK · linked to my_hours_time_logs
clients	`my_hours_clients`	id PK · linked to my_hours_time_logs

FAQ

How does Datrise handle My Hours's custom fields in Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the My Hours to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect My Hours to Azure Synapse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.