Business Intelligence Blogs

View blogs by industry experts on topics such as SSAS, SSIS, SSRS, Power BI, Performance Tuning, Azure, Big Data and much more! You can also sign up to post your own business intelligence blog.

«November 2015»

DirectQuery in Power BI Desktop

In the latest Power BI Desktop a new Preview features was released that now allows you to connect using DirectQuery to either SQL Server or Azure SQL Databases.  DirectQuery is a really neat feature that allows you to point to the live version of the data source rather than importing the data into a data model in Power BI Desktop. 

Normally when you want to get an updated dataset in the Power BI Desktop you would have to manually click the refresh button (this can be automated in the Power BI Service), which would initiate a full reimport of your data.  This refresh could take a variable amount of time depending on how much data your have.  For instance, if you’re refreshing a very large table you may be waiting quite a while to see the newly added data. 

With DirectQuery data imports are not required because you’re always looking at a live version of the data.  Let me show you how it works!

Turning on the DirectQuery Preview

Now, because DirectQuery is still in Preview you must first activate the feature by navigating to File->Options and settings->Options->Preview Features then check DirectQuery for SQL Server and Azure SQL Database


Once you click OK you may be prompted to restart the Power BI Desktop to utilize the feature.

Using DirectQuery in Power BI Desktop

Next make a connection either to an On-Premises SQL Server or Azure SQL database.

Go to the Home ribbon and select Get Data then SQL Server.


Provide your Server and Database names then click OK. ***Do not use a SQL statement.  It is not currently supported with DirectQuery***


From the Navigator pane choose the table(s) you would like to use.  I’m just going to pick the DimProduct table for this example and then click Load.  You could select Edit and that would launch the Query Editor where you could manipulate the extract.  This would allow you to add any business rules needed to the data before visualizing it.


Next you will be prompted to select what you want to connect to the data. Again, Import means the data

Read more

The Big Data Blog Series

Over the last few years I’ve been speaking a lot on the subject of Big Data. I started by giving an intermediate session called “Show Me Whatcha’ Workin’ With”. This session was designed for people who had attended a one hour introductory session that showed you how to load data, to look at possible applications … Continue reading The Big Data Blog Series
Read more

Internal error: Invalid enumeration value. Please call customer support! is not a valid value for this element.

  • 20 August 2012
  • Author: BradSchacht
  • Number of views: 1329

If you have done a lot of work with SQL Server Analysis Services (SSAS) you may have seen this message:

We've all been there. A build error. I tend to get this because I like to forget commas when modifying calculations in the MDX section of the cube editor. It's a fun little game I like to play to keep myself on my toes...question mark?? Anyway, what follows this message box is usually something that you can go fix, like adding the comma or semicolon back into the calculate script. Sometimes, however, you may see the much less friendly:

Internal error: Invalid enumeration value. Please call customer support! is not a valid value for this element.

If you're like me, the first thing you thought was "Well that can't be good." The second thing I thought was "Well of course that's not valid, there is no customer support number listed." But seriously, if you have attended a Pragmatic Works SSAS workshop or a BI Bootcamp with any number of our trainers chances are you have seen this error pop up. Just about the only time I ever get this message is when I am teaching a class and processing the cube over and over and over.

Occasionally I will get this in development, again when doing small cube changes on my laptop and processing the cube a lot. I have never seen this in a production environment, which is not at all to say it hasn't or won't happen.But for peace of mind before people start freaking out this is not a super common error message to see and even less frequent in production from my experience.


Now for the slightly unfortunate part: The Solution. The only way I personally know how to fix this issue is to go to the SSAS server in management studio, delete the SSAS database and redeploy the solution. The unfortunate part is the cube has to be reprocessed along with all the dimensions which could take a long time if you were just making a small calculation change and ended up with this error. The good news is that all your data SHOULD be available in the source system, and you will definitely have all the cube structure still in your solution inside BIDS (or Data Tools)

Note: While the tabular model has not been out nearly as long as multidimensional (and I have not done extensive development in tabular), to date I have only seen this error in the multidimensional format of SSAS.

Have you seen this error before? Did you have a way to fix this without deleting and redeploying? Have you gotten this same error message while working with tabular?

Rate this article:
No rating


Other posts by BradSchacht

Please login or register to post comments.