In our previous blog post, we explained how we can use VertiPaq Analyzer to analyse the amount of memory our model needs. This memory is also linked to the speed with which the model calculates and refreshes data. In this blog series, we’ll discuss several ways to limit this memory usage.
One of the things you could do to refresh your data quicker and speed up calculations is resizing the data model. But how do you even figure out the current size of your data model? Is it the same as its file size?
Most Power BI users are impressed with the possibility to create custom visuals, which sometimes results in very colourful reports/dashboards – and occasionally even leads to documents that teeter on the edge between looking professional or amateurish. Where do you need to draw the line?
Like several similar solutions, Power BI works best if data are structured in a star schema, which is a structure that consists of fact and dimension tables. Typically, one of these dimensions is the date dimension. This dimension can filter your data based on calendar-type fields. If there are multiple Date fields in the fact table (such as OrderDate, DueDate, ShipDate…), there are some considerations to take into account.
As mentioned in earlier posts, Power BI uses an expression language called DAX (Data Analysis Expressions) to create calculations. At first glance, this language is similar to Excel formulas, but there are some important differences. Most importantly, DAX uses a row and filter context when executing expressions.
When you start using DAX, you might think that it looks strangely much like Excel formulas – but while they do look similar, they work in completely different ways. In order to execute calculations correctly, it’s important that you understand these differences.
Can’t get enough of Excel? Good! In this blog post, we’ll teach you another Excel trick. When Microsoft introduced tables in Excel in 2007, it became impossible to use the dollar sign ($) to lock rows or columns. This isn’t much of a problem for rows, but what about columns? Read on – I’ll explain how you can still lock these.
This is the seventh and last blog post in our series about how you can speed up data transformation in Excel VBA. In this blog post, we’ll discuss how you can merge two tables and add them to one recordset.
This is the sixth in a series of 7 blog posts that delve deeper into how you can speed up data transformation in Excel VBA. In the previous blog post, we explained how you can save data in a recordset. This time, we’ll show you how to use this technique to open all files in a folder and transfer their data to a target file.