DataTugPull more from your data
Open app
☰

For your role · Data analysts and BI

For analysts: join and understand your data

A good question often crosses sources. DataTug keeps them in one project, lets you join across them, and records what columns mean, so the next analysis does not start from a blank ON clause.

Explore the demo project All roles
Watercolor of an analyst at a cartographer’s table drawing one route across two charts of the same coast, with blank index cards and a tugboat model on the sill.

The answer needs two databases, so it starts with two exports and a spreadsheet. And I am never sure the IDs mean the same thing.

Your day

  • Exports and spreadsheets. Combining two databases means CSVs and VLOOKUPs, and the numbers drift from the source.
  • Columns that look alike. customer_id here and CustID there: the same thing, or not? The person who knows is busy.
  • Answers without their query. A chart goes to the meeting; the query that made it stays on your laptop.

One task, before and after: compare sales with support load per customer

Who: Data analysts and BI

Today

4 tools2 hand-offsno shared password

  1. You · Database exportExport customers and orders from one database, tickets from another.
  2. You · SpreadsheetMatch the IDs in a spreadsheet.
  3. Colleagues · ChatAsk around what each ID column means.
  4. The meeting · ScreenshotSend a screenshot of the chart.
Today4 tools · 2 hand-offs · no shared passwordExport customers and orders from one database, tickets from another.Match the IDs in a spreadsheet.Ask around what each ID column means.Click to see

With DataTug

1 workspace0 hand-offsno shared password

Some steps are planned or in development.

  1. YouQuery both databases from one workspace and join them.Cross-source TugQL joins in the browserIn development
  2. Whoever knows, onceRecord what a column means, so the next person knows which ID is which.Column meaningsAvailable
  3. MeaningGraphHave MeaningGraph suggest the join between two sources (planned).MeaningGraph integrationPlanned
  4. Your readersShare the result as a dashboard or a saved query, not a screenshot.DashboardsAvailable
With DataTug1 workspace · 0 hand-offs · no shared passwordQuery both databases from one workspace and join them.Record what a column means, so the next person knows which ID is which.Have MeaningGraph suggest the join between two sources (planned).Click to see

Each step names the part of DataTug it relies on and that part’s status today. “Planned” and “In development” steps describe where the product is going, not what you can use now.

Solutions for you

Also useful: Data Quality & MonitoringSafe Data Access

Read more: Reconciling exports by hand

Try it on sample data

The public demo project opens in the browser with sample Northwind and Chinook data. No sign-up.

Explore the demo project