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.

«February 2016»

Power BI Publish to Web for Anonymous Access is Here

Earlier this week on Wednesday the Microsoft Power BI made an incredibly exciting announcement and released Power BI “publish to web” as a preview feature. This is HUUUUGE news! This was probably the top requested feature and its finally here thanks to the hard work and dedication of the Microsoft Power BI team!

Read Getting Started with R Visuals in Power BI

Power BI “publish to web” allows you to easily expose a Power BI report to the world through an iframe that can be embedded wherever you like.

To publish your Power BI report to the web, log into your Power BI site.

Find the report that you want to share and click File in the top left.
Power BI publish to web

You’ll see a message pop up box similar to below. Click the yellow button to create the embed code.
Power BI publish to web preview

This is where you’ll see a very important warning!
WARNING: Reports that you expose through the “publish to web” feature will be visible to everyone on the internet! This means NO AUTHENTICATION is required to view the report that is embedded in your application.
warning 2

Once you do that, you’ll receive an embed code that you can then use to expose your Power BI report within your blog as seen below!

As you can see the report maintains all the interactivity features of Power BI. And as your Power BI report updates and changes, those changes will be reflected in your embedded Power BI reports!

Pretty awesome!

Additional Resources

Read the Power BI “publish to web” announcement here.

Read the Power BI “publish to web” documentation here.


Let me know what you think of this feature or if you have any questions. Leave a comment down below.

Read more


Non Empty vs NonEmpty

Hey everyone, in this blog I want to address a very common MDX Question. What is the difference between the NON EMPTY keyword and NONEMPTY function? To take it a step further which one should you use?

Non Empty keyword VS NONEMPTY Function.

The big difference between the NON EMPTY keyword and the NONEMPTY function is when the evaluation occurs in the MDX. The NON EMPTY keyword is the last thing that is evaluated, in other words after all axes have been evaluated then the NON EMPTY keyword is executed to remove any empty space from the final result set. The NONEMPTY function is evaluated when the specific axis is evaluated.

Should I use NON EMPTY keyword or NONEMPTY function?

Ok Mitchell, so you told me when each of these are evaluated but really you haven’t told me anything up until this point. Can you tell me which one I should use already? Well, unfortunately, it depends. Let’s walk through an example of each using the BOTTOMCOUNT function.


In this example I’m returning the bottom ten selling products for internet sales. Notice that I have returned all products that have no internet sales, this is not necessarily a bad thing, maybe you want to return products that don’t have sales.


However if you don’t want to return these products then we can try using the NON EMPTY keyword. In the below example you can see the results when I add NON EMPTY to the ROWS axis.


WHOOOAAA, what happened?? A lot of people would have expected the results here to show the bottom ten products that DID have sales. However, that is not the case, remember that I said the NON EMPTY keyword is evaluated LAST after all axes have been evaluated. This means that first the bottom ten selling products which have $0 in sales are first returned and then the NON EMPTY keyword removes all that empty space from the final result.

BOTTOMCOUNT function with NONEMPTY function.

So let’s try this again, if you want to return the bottom ten products that had sales then we must first remove the empty space before using the BottomCount function. Take a look at the code below:


In this code we first remove the empty space before using the BOTTOMCOUNT function. The result is we return the bottom ten products that had internet sales. Once again neither one is right or wrong here it just depends on what you want in your final result.

NON EMPTY Keyword vs. NONEMPTY Function – Performance

There is a very common misconception that the NONEM

Read more

Build Configurations in SSIS 2012

  • 8 July 2012
  • Author: cprice1979
  • Number of views: 28320

Although not new in SSIS 2012, Build Configurations have become exponentially more useful with the introduction of parameters and the new project deployment model. Before we dive in to see how useful this feature is, let's take a moment to review parameters and the project deployment model.


Parameters are a new feature intended to replace and simplify configuration of SSIS packages when running under the new project deployment model. They are treated like read-only variables and have options that can make them required or mark them as sensitive. Parameters can be either package or project level and they are visible to both the Execute Package task and to SQL Agent.

Project Deployment Model

The new project deployment model brings together connections, configuration and packages into a single-deployable unit, the *.ispac file. This file is then deployed to the Integration Services Catalog, which is also new in 2012. This new model opens up several new possibilities, some of which are shared project connection managers, project references and of course project parameters.

Build Configurations

If you have worked with SSIS extensively, more than a couple times you will have found yourself debugging a package only to realize that a connection string it pointed to the wrong source or destination. Keeping track of these values across different environments or servers can be tedious, time consuming and error prone. Build Configurations are intended to simplify and help you avoid these types of situations.

First, off you can define multiple solution configurations (i.e. Development, Acceptance, & Production) by using the Configuration Manager in SQL Server Data Tools (formerly BIDS). If you have multiple projects within your solution, each project has its own context and can be mapped to the appropriate configuration.

Solution Build Configuration Control
Configuration Manager

The first part to these design-time configurations is parameter binding. You launch the parameter binding dialog by click the 'Add Parameters to Configurations' icon. From this dialog you can add, remove and sync parameter values to solution configurations. This is handy in the case of our connection string example because we now can configure the proper environment parameter values and easily switch between environments by changing the solution or build configuration.

Add Parameter to Configuration
Parameter Value Management

The second part is binding project configuration properties to the build configuration. Project configuration properties fall into one of three categories: Build, Deployment & Debugging. These properties behave in the same manner as configuration bound parameters. The most useful of these is the deployment target server and server project path. The scenario is easy, your development, staging and production servers should all be different target server names or at a minimum server project paths. By configuring the build configurations you could easily switch from environment to environment without ever worrying about entering the correct server name or path.

Project Property Management

I hope this brief blog has helped you see the value in build configurations in SSIS 2012.

Till next time!!


Categories: Analysis Services
Rate this article:
No rating


Other posts by cprice1979

Please login or register to post comments.