Skip to content
Analytics ⇄ Database

Microsoft Power Bi to TiDB integration — real-time data sync

Keep Microsoft Power Bi and TiDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Microsoft Power Bi and TiDB

Give Microsoft Power Bi the users, events, and records that live in TiDB in real time, and sync the cohorts and scores Microsoft Power Bi computes back into TiDB where your applications read them.

Microsoft Power Bi is a read-only source: Stacksync reads its data in real time and delivers it into TiDB, so TiDB always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.

A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Microsoft Power Bi is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from TiDB into Microsoft Power Bi usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.

Common use cases

  • 01 Pull Dataflow and Datasource definitions to document lineage between Power BI and its upstream warehouses in a governance database.
  • 02 Load dataset Refresh History into an operational database to alert on-call teams when scheduled refreshes fail or run long.
  • 03 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
  • 04 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics

Common sync patterns

Analytics on live operational data, minus the pipeline

The users, events, orders, and records stored in TiDB land in Microsoft Power Bi as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.

One version of each user or account

A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.

Filter and grouping dimensions kept fresh

Attributes teams slice by, such as plan, region, or account owner, stay current in Microsoft Power Bi because they sync from TiDB as they change, instead of going stale after a one-time import.

What you can sync between Microsoft Power Bi and TiDB

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Microsoft Power Bi objects TiDB objects How this pairing syncs
Reports Report definitions and metadata read via GET /reports and per-workspace GET /groups/{id}/reports; enumerated to mirror the content inventory into a catalog. Columns MySQL-compatible types mapped to fields in the paired system. Reports is specific to Microsoft Power Bi and Columns to TiDB — each maps to any object or custom field on the other side.
Dashboards and Tiles Dashboards and their pinned tiles read via GET /dashboards and /dashboards/{id}/tiles; inventoried to map dashboard content back to its source datasets. Indexes Secondary indexes that keep incremental sync queries efficient. Dashboards and Tiles is specific to Microsoft Power Bi and Indexes to TiDB — each maps to any object or custom field on the other side.
Dataflows Power Query ETL definitions read via GET /groups/{id}/dataflows; used to document lineage from upstream sources into datasets. Sequences Server-side ID generation relevant when external systems write rows. Dataflows is specific to Microsoft Power Bi and Sequences to TiDB — each maps to any object or custom field on the other side.
Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Databases MySQL-style schemas addressed by any MySQL-compatible client. Datasources and Gateways is specific to Microsoft Power Bi and Databases to TiDB — each maps to any object or custom field on the other side.
Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Refresh History is specific to Microsoft Power Bi and Tables to TiDB — each maps to any object or custom field on the other side.
Workspaces (Groups) Containers for content read via GET /groups (tenant-wide via GET /admin/groups); mirrored to reproduce the tenant's content hierarchy in a catalog. Views Logical views for shaping reads before syncing outward. Workspaces (Groups) is specific to Microsoft Power Bi and Views to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Power Bi and TiDB

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Microsoft Power Bi TiDB Interval-based propagation

DetectionStacksync polls Microsoft Power Bi for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: no webhooks or change-data-capture.

DeliveryEach detected change is applied to TiDB as a row-level write, with types converted between the two schemas.

TiDB Microsoft Power Bi Sub-second propagation

DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.

DeliveryMicrosoft Power Bi does not accept inbound record writes, so this direction carries requests rather than records: Microsoft Power Bi's output flows back as field updates on the originating TiDB records.

Rate-limit considerations

  • Microsoft Power Bi: Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Microsoft Power Bi ⇄ TiDB

Connect Microsoft Power Bi and TiDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Power Bi–TiDB connection.

Real-time

Real-time sync

Changes in Microsoft Power Bi or TiDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Power Bi or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Microsoft Power Bi or TiDB record.

Observability

Monitoring

Track your Microsoft Power Bi ⇄ TiDB sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Power Bi and TiDB.

How the Microsoft Power Bi and TiDB connectors work

Microsoft Power Bi

Integration surface
Power BI REST API, including the Execute Queries (DAX) endpoint and admin scanner APIs; a read-write XMLA endpoint is available on Premium, Premium-Per-User, and Fabric capacity.
Authentication
Microsoft Entra ID (Azure AD) OAuth 2.0 bearer tokens. Supports delegated user tokens and app-only service principals; service principals must be enabled under the tenant's Developer settings and granted workspace access. Tenant-wide admin reads require the Tenant.Read.All scope.
Change detection
Pull-based: no webhooks or change-data-capture. Content is polled via REST list endpoints, dataset changes are inferred from Refresh History and the admin Activity Events audit log, and the scanner API's GetModifiedWorkspaces reports workspaces changed since a given time.
Capabilities
read
Rate limits
Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas
How it works

How to connect Microsoft Power Bi to TiDB — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Microsoft Power Bi and TiDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Microsoft Power Bi connected
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft Power Bi and TiDB objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Microsoft Power Bi ⇄ TiDB
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Microsoft Power Bi TiDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Microsoft Power Bi and TiDB integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 361 integrations available for Microsoft Power Bi and TiDB.

Popular · 7 of 361
All Microsoft Power Bi integrations All TiDB integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own