← SWAP CENTER
SWAP PATH · DATA PLATFORM

Databricks to e6data

Point your BI connection at e6data and run any workload at lower cost, at the same or better performance.

THE SWAP, STEP BY STEP

Add e6data to Databricks in five steps

ESTIMATED SWAP TIME [Step 3 excluded] A few hours or less

  1. Create a cluster

    In your e6data workspace, start XS with one executor (1 vCPU). Load-based sizing and auto-suspend handle the rest.

    READ THE GUIDE ↗
  2. Connect Unity Catalog

    Generate a Databricks API token with Unity Catalog access and paste it into your e6data workspace with the workspace host. Your tables, schemas and policies carry over as-is.

    READ THE GUIDE ↗
  3. Pick the workload

    Identify the query and its source (a BI dashboard, an agent, an API call), run it, and verify it’s the right one by checking that Databricks’ query history detects it, before you move it.

  4. Swap the connection

    In your data tool’s editor or advanced settings, re-point the data source to e6data, using your cluster host and an access token.

    READ THE GUIDE ↗
  5. Verify and publish

    Check that the query and catalog appear in e6data as expected, then publish your workload to production for the cost and latency improvements on live traffic.

PLATFORM WALKTHROUGH: CREATE AND CONFIGURE A CLUSTER

CHANGES VS. STAYS

What changes, and what doesn’t.

CHANGES

  • The data source in your BI tool points at your e6data cluster.
  • Queries for that workload run on e6data compute.
  • Cost and latency are billed and measured per query.

STAYS PUT

  • Databricks and your Unity Catalog.
  • Tables, schemas, storage and formats. Nothing is copied.
  • Access policies and governance.
  • Your dashboards, reports and SQL.
GUIDED SWAP

Run your first Databricks swap with us.

Bring the dashboard that dominates your bill. We’ll swap it in your environment and show you the before and after.

Problems we’re solving

An actual person replies, usually within one working day.