A Fine Slice Of SQL Server
Gilbert Quevauvilliers tries it:
Did you know that there is an easy way to run and extract Power BI REST API data?
The good news is that you can do this directly in your web browser. You don’t have to install or configure anything!
The method below works well if you want to either test the API to see what it returns.
Or if you want to run it to extract some data.
Read on for the process.
Comments closedJason Cockington makes several recommendations of external tools for Power BI Desktop:
The External Tools ribbon is a feature that has been available in Power BI Desktop since the July 2020 release. This feature should be considered essential to anyone who is regularly working in the Power BI space. In this article I recommend my top five External Tools, that I consider essential to any Power BI developer.
Read on for the recommendations. I regularly use two of the five but these do look good.
Comments closedChris Webb does some compacting:
Power BI can handle large data volumes, but just how much data can you load into Power BI? Can Power BI handle big data? How big is “big” anyway? These are questions you may have when you’re starting out on a new Power BI project and the answers can be hard to find. Indeed the answer in most cases is “it depends”, which isn’t very helpful. In this post I will try to explain the various limits on Power BI dataset size and how you can know if you’re likely to hit them.
Click through to learn more about these limitations.
Comments closedThe Power BI service can handle a lot of data, but just because your data sources are big doesn’t mean that your Power BI datasets will also take up a lot of space. If the data model is designed efficiently, even terabytes of source data will usually translate into megabytes, or a few gigabytes of dataset storage at most. As the industry has largely made the transition from on-prem SQL Server Analysis Services and AAS tabular models to Power BI datasets in Premium capacity, the size limits in the cloud service are notable. The following reference chart from the Microsoft Learning docs shows that a P1 Premium dedicated capacity is limited to 25 GB per dataset. That’s a lot but there are Premium capacity SKUs that can handle up to 400 GB of compressed data in an in-memory data model.
Click through for Paul’s introductory thoughts and stay tuned for part 2.
Comments closedSomething cool has just been announced for Azure SQL DB: the ability to call a limited number of REST APIs direct from TSQL. The announcement is here:
Read on for sample code, including a way to execute DAX queries from T-SQL.
Comments closedChris Webb reminds us that Power BI incremental refresh can lead to some fragmentation:
A lot of people are building large datasets in Power BI Premium nowadays, and if you’re building a large dataset you’re very likely to be using Power BI’s incremental refresh functionality with your fact tables or manually creating and refreshing partitions in them. If so, you should occasionally do a special kind of refresh to shrink the dictionaries on your fact tables.
Read on for a test of the most extreme scenario, though even less extreme versions can be bad.
Comments closedGilbert Quevauvilliers gets the last word:
Power query can be so powerful and once again it came to my rescue.
I had a requirement where I wanted to append some text to the end of each of the column names in my table.
To do this I did the following below.
Click through for the solution.
Comments closedGilbert Quevauvilliers keeps to the schedule:
Below are the steps on how to use Power Automate to schedule a refresh of a Power BI dataset at the time you want it to.
I have recently seen some questions in the Power BI Community with regards to refreshing Power BI datasets. I thought it would be a good idea to blog on how to use Power Automate (Flow) to schedule a refresh of a Power BI Dataset.
Read on to see what the limitation is in Power BI and how you can use Power Automate to get around it.
Comments closedChris Webb doesn’t want to wait:
There are four columns: Date, Town and two measures. One measure called [Fast Measure] is, as the name suggests, very quick to execute; the other measure, called [Slow Measure], is very complex and slow. The definitions are irrelevant here. Notice that there is a filter on this table visual so only the rows where [Fast Measure] is greater than 1 are shown.
If I measure the amount of time to render this table in Performance Analyzer, it takes around 17.5 seconds to run. However, if I remove the filter on [Fast Measure], the table only takes 8 seconds to run. Why? The filter is on the fast measure and surely more rows are returned without the filter, so wouldn’t the slow measure be evaluated more?
Click through for the answer.
Comments closedMara Pereira shows us a trick:
Have you ever wondered if you can apply conditional formatting based on a text field/measure instead of a numeric field/measure?
If your answer is yes, then this trick is for you!
The other day I was working with a customer who asked something that I had no idea how to build.
They wanted to apply conditional formatting over some of their visuals, but they wanted the conditional formatting applied over a text field and not over a numeric field or a measure.
Read on to see how.
Comments closed