cancel
Showing results for 
Search instead for 
Did you mean: 
Community Articles
Dive into a collaborative space where members like YOU can exchange knowledge, tips, and best practices. Join the conversation today and unlock a wealth of collective wisdom to enhance your experience and drive success.
cancel
Showing results for 
Search instead for 
Did you mean: 

Forum Posts

Agre_Celebal
by New Contributor II
  • 1202 Views
  • 0 replies
  • 1 kudos

The Comparison: Why the Alternatives Fall Short for Databricks-Native Agentic Systems

The OLTP architecture your agentic systems actually need, and how it compares to Supabase, Azure PostgreSQL, and Cosmos DBEarlier this year, Nikita Shamgunov — the engineer leading Databricks Lakebase — published a number that reframed my entire arch...

Blitzkrieg_2-1781631361677.png
  • 1202 Views
  • 0 replies
  • 1 kudos
szymon_dybczak
by Esteemed Contributor III
  • 483 Views
  • 0 replies
  • 1 kudos

Databricks Lakehouse Replay

Has anyone here looked at the new Databricks Lakehouse Replay feature?Lakehouse Replay | Databricks on AWSDatabricks can now automaticaly take a small subset of safe, read-only workloads from your workspace and replay them against upcoming runtime ve...

  • 483 Views
  • 0 replies
  • 1 kudos
WiliamRosa
by Databricks Partner
  • 319 Views
  • 2 replies
  • 2 kudos

We Reached 500 Members in the São Paulo Databricks User Group

Today, we’re celebrating a very special milestone: the São Paulo Databricks User Group has reached 500 members.More than just a number, these are 500 professionals united by a shared passion for data, AI, analytics, data engineering, and innovation. ...

banner_500.png
  • 319 Views
  • 2 replies
  • 2 kudos
Latest Reply
WiliamRosa
Databricks Partner
  • 2 kudos

Thank you, @Advika !We're very proud of this milestone and grateful to everyone who has contributed to building and growing the São Paulo Databricks User Group community.Thank you for your support!

  • 2 kudos
1 More Replies
Debasis_Pal
by New Contributor II
  • 489 Views
  • 2 replies
  • 2 kudos

Resolved! Refresh PBI Dataset is consuming unnecessary compute

If I call powerbi refresh from databricks workflow job it waits until the refresh is complete unlike ADF(Azure Data Factory) pbi refresh through rest api. In case of big pbi dataset which might take more than a hour to refresh in databricks compute r...

  • 489 Views
  • 2 replies
  • 2 kudos
Latest Reply
szymon_dybczak
Esteemed Contributor III
  • 2 kudos

Hi @Debasis_Pal ,The current Power BI task that is available in databricks workflow will wait for refresh process to return correct status (whether it succeeded or failed).If you need to replicate the same behaviour as in ADF you can start refresh pr...

  • 2 kudos
1 More Replies
Brahmareddy
by Esteemed Contributor II
  • 1265 Views
  • 7 replies
  • 8 kudos

Grocery Data Intelligence: Smart Grocery Planning with Data + AI

Hi Databricks Community,For the DAIS 2026 Community Virtual Contest, I built a project called Grocery Data Intelligence. This is a Smart Grocery Planning solution with Data + AI, built using Databricks Free Edition.The idea came from a very simple re...

  • 1265 Views
  • 7 replies
  • 8 kudos
Latest Reply
Brahmareddy
Esteemed Contributor II
  • 8 kudos

Thank you all for your feedback, review, and suggestions.I also received some very helpful feedback from the Reddit Databricks community, especially around making the architecture clearer, improving the action flow, and simplifying the app story.http...

  • 8 kudos
6 More Replies
antoalphi
by New Contributor III
  • 739 Views
  • 2 replies
  • 1 kudos

Databricks Lakeflow Connect for MySQL

In Databricks Lakeflow Connect for MySQL (currently in public preview), Databricks recommends limiting each ingestion pipeline to around 250 tables, with validated testing up to 1 TB of snapshot data.However, in real-world enterprise scenarios, custo...

  • 739 Views
  • 2 replies
  • 1 kudos
Latest Reply
Lu_Wang_ENB_DBX
Databricks Employee
  • 1 kudos

TLDR: Do not scale Lakeflow Connect for MySQL linearly by creating dozens of identical pipelines. Current guidance is ~250 tables per pipeline, with a hard limit of 1,000 flows / ~500 tables, and the MySQL connector has been tested at 100 tables with...

  • 1 kudos
1 More Replies
Labels