Forum Discussion
direct query limitations
I would suppose that they know that DQ on SQL is not really usable at the moment. Let's see whether we will see a few improvements in the future. :) At least the stuff with Measures / calc columns should be mandatory.
But look at it this way:
AS Tabular / MD
- we started with "importing" AS Tabular models from a server into a PBIX
- AS conncetor was published, allowing direct connect
- AS Connector was enriched by feature to import MD models
- ... live connect to MD models?
Azure SQL DB
- Azure SQL DB could only use direct connect via Webservice, PBI desktop could only use "import"
- Azure SQL DB can now be accessed via PBI Desktop in live-connect mode
SQL DB on-prem
- Only import mode was possible
- live connect has been enabled
As SQL DBs are lacking the dynamic stuff we have in MD and Tabular models, we have a strong argument in favor of improved dynamics in SQL DBs. Also because in regards of Azure, IaaS is quite expensive and PaaS (Azure SQL DB) is not. Let's be excited.
I had hoped the new DEcember release with "Enter Data" option may have resolved at least adding an additional flat table directly into my data model which would work alongside the existing Direct Querytables. Instead no we are still asked to switch to upload if i wish to use both "Direct Query" & "Enter Data".
But yes the minimum in DC of measures etc is essential and I am sure they are working on it.
I still get the same error message? Is there any fix to this that I am not aware?
Thanks!
