Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
Victormar
Helper V
Helper V

Missing data when replugging model

Hello community,

 

I am facing a very odd situation, and I feel I have tried everything I could and it still doesn't work.

I have a report that is connected to Azure Databricks, to one database where I developed it. Two weeks ago we created a replica of this database because we are changing the structure in Databricks; So, I replugged the report to this new database, and I lost some data.

 

We have one main dimension table, which has the vehicles and it's keys. Then we have fact tabels with measurements like mileage, speed, and so. They connect in the model using keys.

 

When replugged, the vehicle ids from the different tables don't match. I removed all the filters and conections and still it doesn't work.

 

Just to be clear, if I get the old report, connected to the old database, and I refresh it, all works fine. If I add the new database via parameter, and try to switch between both of them, then the report seems to crash. 

 

Could it be a problem because both databases are connected to the same cluster in Databricks? I have no idea to what to try anymore.

 

Thanks in advance for any help 🙂

 

 

1 ACCEPTED SOLUTION
v-heq-msft
Community Support
Community Support

Hi @Victormar ,
Based on your description that you changed the structure in Databricks, the first thing we need to make clear is that you need to make sure that the schema of the new database is the same as the old one. Any differences in table structures, data types or relationships can cause problems when switching databases. Secondly, since both databases are connected to the same cluster, there may be caching issues. Try clearing the cache in Databricks to ensure that the latest data is used. Finally, after switching to the new database, perform a full data refresh. This helps to synchronize the data and resolve any discrepancies.
CLEAR CACHE - Azure Databricks - Databricks SQL | Microsoft Learn

Best regards,
Albert He


If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

View solution in original post

2 REPLIES 2
Victormar
Helper V
Helper V

Hello!

 

Thanks for your reply, really good to know.

 

It turns out in the end the problem was that I had two functions to change between environments, and I only updated one, I totally missed the other one (was hidden between the tables ;P)

But your explanation @v-heq-msft it's super good to know, thanks 🙂

v-heq-msft
Community Support
Community Support

Hi @Victormar ,
Based on your description that you changed the structure in Databricks, the first thing we need to make clear is that you need to make sure that the schema of the new database is the same as the old one. Any differences in table structures, data types or relationships can cause problems when switching databases. Secondly, since both databases are connected to the same cluster, there may be caching issues. Try clearing the cache in Databricks to ensure that the latest data is used. Finally, after switching to the new database, perform a full data refresh. This helps to synchronize the data and resolve any discrepancies.
CLEAR CACHE - Azure Databricks - Databricks SQL | Microsoft Learn

Best regards,
Albert He


If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.