There exists more to these two visualization tools than meets the eyes:
It will depend on your SQL Storage space instance if you need to take the benefit of MDX with Tableau in multidimensional mode or DAX using Power BI in Tabular mode.
SQL Storage space instances can be in Tabular function, which can use DAX features or you can run an instance in Multidimensional mode, which may use MDX on Multidimensional cubes. You should take special take note that Power BI can use DAX, but Tableau is unable to use DAX. Cadre uses MDX on cubes in Multidimensional mode.
The benefit of the Multidimensional mode is it can cater to far more storage room than your data system can take upwards, with support of over a, million rows.
The benefit of the Tabular model is that DAX is a lot much easier to apply with fewer difficulties on Listar models and Power BI supports DAX directly. In reality, if you are using Kusto-Azure data lakes, you can create application ideas coding that can be directly transferred to Power BI Training as a textual content script for visualization/analytical purposes. Data storage place data marts are usually defined in Tabular mode, because of their constraint to size in space for storing and line counts. Multiple data marts applied collectively hold huge sums of data, which Multidimensional would profit. Another benefit of Listar mode is that you can pull n drop human relationships from the main key table to the Foreign key desk, Multidimensional cannot.
You should also note that the Tabular model emerged this year on SQL Server, Power BI, and Exceed also use DAX, but cannot use MDX scripting. Tableau cannot use DAX but can use MDX scripting on cubes with data warehouses.
I would expect Microsoft to support more than one million series and storage in the future, but still waiting to see this happen.
Visualization tools (Tableau/Power BI) are reasonably easy to learn, but DAX now is easier, in the beginning, to learn than MDX, because MDX is based on series and child/parent connection locations while cutting dimensions to determine measures. DAX pin number points measures according to table columns, which is more individual in manners of thinking.
And so the answer is mostly in the language each visualization tool utilizes and the purpose of storage/row counts in the database centered on the function.
Let's not overlook also on Power BI modes (Direct Query limitations compared to Cached Querying). The particular limitations in Immediate query are no hierarchies, certain functions cannot apply, but the mode is near real-time modernizing. Cached, you will need to set intervals to when it improvements in line with the SQL data changes.
Please review the advantages and downsides and first decide what exactly is right for you. Though these toolsets do the same task, they are two completely different animals.
You can also visit my YouTube link: https://youtu.be/4stvuDKPFzM
