Demo on Databricks Free Edition
You can try the complete MDMongoose — app, pipelines, jobs and golden records — on Databricks Free Edition, at no cost and without a credit card. The setup takes about 20 minutes, most of it waiting for the first deployment and the init job. You need no local tools: everything happens in the browser.
What you get
The demo seeds realistic, invented data that behaves like real sources do — the same company spelled differently per system, missing VAT IDs, typos and stale values:
| Branch | Content |
|---|---|
| Customer | 1 000 companies in 7 countries from three sources: SAP kna1, Salesforce account and a webshop, matched into golden records |
| Supplier | 200 companies from SAP lfa1 and Coupa |
| Employee | 300 people from Workday and Active Directory |
| Product | 50 products in a six-level hierarchy, entered by hand |
| Reference Data | Countries and the source records as loaded |
1. Create a Free Edition account
- Go to databricks.com/learn/free-edition and sign up with an e-mail address, Google or Microsoft.
- You get one workspace with Unity Catalog. It already has the catalog
workspaceand a SQL warehouse called Serverless Starter Warehouse — exactly what MDMongoose uses by default, so nothing needs to be configured.
2. Add the repository as a Git folder
- In the workspace, open Workspace in the left menu, then your home folder.
- Click Create → Git folder.
- Paste the URL of the MDMongoose repository (see Resources), keep the provider GitHub, and click Create Git folder. A public repository needs no Git credentials.
3. Deploy the bundle
- In the Git folder, open
databricks.yml. - Click the Deployments icon (the rocket) on the left of the editor.
- Select the target free (the default) and click Deploy. Confirm the resources it lists: the app,
the jobs
mdm_init,mdm_load,mdm_actionandmdm_refresh, the pipelinesmdm_loadandmdm_export, and the schemasmdm_core,mdm_stagingandmdm_export. - Wait for Deployment succeeded (one to three minutes).
4. Run mdm_init
- In the same Deployments panel, under Bundle resources, find the job mdm_init and click Run (▶).
- Follow the run under Jobs & Pipelines. On Free Edition it usually takes 10–20 minutes. It:
- creates the
MDMNodestable and the system definitions; - creates the seven demo source tables in
mdm_stagingwith change data feed; - loads them through the
mdm_loadpipeline and builds the golden records for Customer, Supplier and Employee; - grants the app's service principal access, and runs the
mdm_exportpipeline once.
- creates the
On Free Edition you are the workspace admin, so the grants normally succeed. If the run output says it could
not grant access, open sql/grants.sql from the Git folder in the SQL editor and run it once.
5. Start the app
- Go to Compute → Apps and open mdm.
- Click Start if it is stopped, and wait until it is Running. The first start builds the UI and takes a few minutes.
- Click the app's URL. Sign in with your Databricks account when asked, and allow the app to act on your behalf.
You land on MDM, the root of the hierarchy. As the workspace admin, you are an MDMongoose admin too.
6. Take the tour
| Try this | Where | Read more |
|---|---|---|
| Open a golden record and its three source records | Master Data › Customer → any record | Master data records |
| Explode the customers in the grid, sort, filter, paste | Master Data › Customer → Edit Children | Edit Children |
| Run a dry run of the matching | Master Data › Customer → Refresh Golden Records | Matching |
| Change a survivorship rule and simulate it | Model › Rules → Customer survivorship v2 → Edit Rule | Survivorship rules |
| Walk a six-level product hierarchy | Master Data › Product | Modifying data |
| Load changes from a source | Reference Data › SAP ECC › kna1 → Load Childs | Importing data |
| Export a branch to Excel | any node → Export | Exporting to CSV and Excel |
| Query an export | SQL editor: SELECT * FROM workspace.mdm_export.customer_golden_records | Materialized views |
| Check what a group may do | header → View as UC group | Security |
To see incremental loading at work, change a source row in the SQL editor and load it:
UPDATE workspace.mdm_staging.src_sap_kna1
SET TELF1 = '+49 89 5550111'
WHERE KUNNR = '0000100234'; -- ACME GmbH
Then click Load Childs on Reference Data › SAP ECC › kna1: only the changed row is merged. Because the table has Run Golden After Load, the golden record ACME GmbH is refreshed too — its Phone uses Most Recent, so the new number wins.
Living within the Free Edition limits
Free Edition is generous enough for the demo, but it has limits. What they mean here:
| Limit | What you notice | What to do |
|---|---|---|
| Apps stop 24 hours after they were started or deployed | The app URL shows that the app is stopped | Start it again from Compute → Apps. All data is in Delta; nothing is lost. |
| One small SQL warehouse | The first screen after a pause takes a few seconds while the warehouse starts | Nothing — later clicks are fast; the app caches what you visited. |
| Daily compute quota | Jobs and the warehouse stop for the rest of the day when it is used up | Keep the hourly mdm_refresh job paused (it is by default); avoid full reloads in a loop. |
| One active pipeline per type, 5 concurrent job tasks | A load started while an export runs waits or fails | Run one load or refresh at a time. |
| Serverless jobs start in about a minute | Load Childs and Refresh Golden Records show a run dialog for a while | Saves in the UI are direct and do not use jobs. |
Starting over or cleaning up
-
Reset the demo: drop the schemas and deploy again.
DROP SCHEMA workspace.mdm_core CASCADE;
DROP SCHEMA workspace.mdm_staging CASCADE;
DROP SCHEMA workspace.mdm_export CASCADE;Then Deploy and run mdm_init again.
-
Remove everything: in the Deployments panel choose Destroy (or
databricks bundle destroy), then drop the schemas as above and delete the Git folder.
Next steps
- Load your own data: Importing data.
- Install on a paid workspace or without demo data: Deployment — set
demoto"false"for a clean install.