Google BigQuery to MicroStrategy Integration

How Datrise loads Google BigQuery into MicroStrategy

Datrise syncs Google BigQuery's datasets, tables, views, query jobs, table schemas, and partitions into MicroStrategy as warehouse tables for MicroStrategy's schema objects. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the warehouse tables behind attributes and metrics, so re-runs update only what changed. Date-partitioned facts. MicroStrategy maps attributes to columns, so Datrise lands stable keys and names so metrics don't break.

Ideal for large-scale enterprise reporting and governance.

Endpoints

Google BigQuery: Serverless analytics warehouse on Google Cloud.

MicroStrategy: Enterprise BI with dossiers, governed metrics, and mobility.

How Google BigQuery entities map to MicroStrategy

Google BigQuery entity	MicroStrategy object	Notes
datasets	`bigquery_datasets`	id PK · custom fields → flattened columns
tables	`bigquery_tables`	id PK · linked to bigquery_datasets
views	`bigquery_views`	id PK · linked to bigquery_datasets
query jobs	`bigquery_query_jobs`	id PK · linked to bigquery_datasets

FAQ

How does Datrise handle Google BigQuery's custom fields in MicroStrategy?

Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MicroStrategy types.

How does the Google BigQuery to MicroStrategy sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the warehouse tables behind attributes and metrics.

Related pipelines

Early access

Connect Google BigQuery to MicroStrategy 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.