Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

smpa01

Datamart breaks when existing table is enhanced

Submitted by Super User on ‎08-17-2022 12:31 PM

I have deployed a datamart and queried tables from different sources (sql, sharepoint, api).

 

However, if I try to enhnace any table by changing the code in PQ window (while being mindful of keeping the number of the column same as well as the order of the column), and load it back to datamart, the datamart breaks, meaning following element breaks

 

Data source credentials

 

smpa01_0-1660764003145.png

Loading data- I expect to see 50k+ rows here, which does not happen.

 

smpa01_2-1660764220341.png

 

Can someone from MS please advise what is going on here?

 

Also, I can query the AZURE SQL tables, but the query execution has some flaws. A super optimized query that executes in 1 second, takes 7 minutes on a subsequest execution. Why is that? How can I access/improve these severs myself?

 

Datamart will be a game changer without these flaws and I need to know all these things beforehand so that I don't tangle myself with prod reports feeding from a datamart that is stale.

 

Status: Needs Info
See more ideas labeled with:
2 Comments (2 New)
Comments
Anonymous
Not applicable
‎08-18-2022 01:05 AM

Hi @smpa01 

You mentioned that you enhnaced any table by changing the code in PQ window , can you explain it in detail ? I don't quite understand what you mean, maybe you can show your actions through screenshots or videos?

 

Best Regards,
Community Support Team _ Ailsa Tao

smpa01
Super User
Super User
‎08-18-2022 06:50 AM

@Anonymous  I queried a table from sql server and set it up in the datamart.

 

Let's suppose that the following query was used when it was set up for the first time

 

select
      col1
      ,col2
      ,col3
from
    fact1 a 
outer apply (select * from dim1 b.....where)
where (predicate)
and exists (predicate)

 

After a couple of days, I received an enhancement req from ops so that the query now becomes

select
      col1
      ,col2
      ,col3
from
    fact1 a 
outer apply (select * from dim1 b.....where)
where (predicate)
and exists (predicate) 
     
union all

select
      col1
      ,col2
      ,col3
from
    fact2 a 
outer apply (select * from dim2 b.....where)
where (predicate) and ..... and ...... and.....
and exists (predicate)

 

Whenever I update/enhance/ my query I am facing challenges like this.

Idea Statuses