My Hours to Microsoft SQL Server Integration

How Datrise loads My Hours into Microsoft SQL Server

Datrise syncs My Hours's time logs, projects, tasks, clients, team members, and billable rates into Microsoft SQL Server 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 a watermark on updated-at, applied with a MERGE statement, so re-runs update only what changed. Optional partitioned tables on a date partition function. SQL Server defaults to a case-insensitive collation, so Datrise preserves original casing in a metadata column to avoid silent key collisions.

Ideal for Microsoft-stack analytics and Power BI Import models.

Endpoints

My Hours: Time tracking and billable hours for projects.

Microsoft SQL Server: Microsoft relational DB with enterprise features.

How My Hours entities map to Microsoft SQL Server

My Hours entity	Microsoft SQL Server 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 Microsoft SQL Server?

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 Microsoft SQL Server types.

How does the My Hours to Microsoft SQL Server sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with a MERGE statement.

Related pipelines

Early access

Connect My Hours to Microsoft SQL Server 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.