![]() ![]() Well, that’s obviously a potential roadblock, but I believe you should be on good terms with your IT/DBA colleagues, nevertheless of access rights:)…So, talk to them, explain the benefits of using views, and I’m sure they will gladly assist in creating and exposing them instead of raw tables. ![]() I hear you, I hear you…You don’t have access to an underlying database. Sticking with this idea, if you have a chance to apply your data transformations on the source side (within the database itself), you should definitely do it! Use views to encapsulate complex logic, perform calculations (don’t forget that calculated columns in Power BI are not optimally compressed), or filter out specific portions of data. ![]() When explaining the best practices for data transformation and shaping, I always like to quote this sentence from the header, which is known as “ Roche’s Maxim” (Roche is Matthew Roche from the Microsoft Power BI team). Stay tuned, we will “demystify” all the pros and cons of using views over tables in your Power BI solutions… #1 “Transform your data as upstream as possible, as downstream as necessary” – Roche’s maxim However, I’m also sure that you may have some concerns about the potential caveats – namely, performance when compared to “regular” tables. With all these advantages in mind, I’m sure you can already assume some of the benefits views can provide when used in Power BI. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |