If you determine that a series of Power Query/M functions are needed then you can get going with PBIX in the short term but preferably the need for this light ETL package can be eliminated with a DW project in the future and for now SSAS doesn’t support Power Query/M as was planned for SSAS 16′: Note: If an SSAS Tabular 2016 development server instance is available and the data transformations required could be handled with SQL queries I’d choose to even start a POC/Pilot project with a Tabular model rather than PBIX. detailed feedback, rapid iterations) contained within these files (or perhaps larger data sources via direct query in PBIX) but ultimately, if the model represents an important business process and/or common business entity (employee, region) any BI organization would prefer (or require) that this data conform to the data warehouse architecture and data governance policies. Yes, you can and should build models in Excel and Power BI Desktop and you can obtain great value from the small scale models (e.g. SSAS (Tabular) is the modeling engine of MSBI and the scalability (ie partitions) and manageability features it provides makes it essential for corporate MSBI Solutions.The content of this post will focus on the highlighted Excel and Power BI Desktop client authoring tools but I think this slide is important to introducing this topic as it implies the following points: In the MS Ignite session Innovate with MSBI in the Enterprise, Kamal Hathi, GM for Power BI, introduced the following slide as ‘BI on your Terms’ and provided a summary of each stage of the lifecycle (Model, Author & Analyze, Deliver, and Consume).
0 kommentar(er)
