DatriseAI-first ETL

Short.io to Microsoft SQL Server Integration

AI-first ETL from Short.io into Microsoft SQL Server. Governed entities, incremental sync, typed landing tables.

How Datrise loads Short.io into Microsoft SQL Server

Datrise syncs Short.io's links, domains, clicks, referrers, countries, and link tags 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

Short.io: Branded short links and click analytics.

Microsoft SQL Server: Microsoft relational DB with enterprise features.

How Short.io entities map to Microsoft SQL Server

Short.io entityMicrosoft SQL Server objectNotes
linksshort_io_linksid PK · custom fields → NVARCHAR(MAX) JSON columns
domainsshort_io_domainsid PK · linked to short_io_links
clicksshort_io_clicksid PK · linked to short_io_links
referrersshort_io_referrersid PK · linked to short_io_links

FAQ

How does Datrise handle Short.io'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 Short.io 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 Short.io 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.