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

Basic Configuration: SourceSafe 2005 and SQL Management Studio 2005

  • 6 June 2011
  • Author: Keith Hyer
  • Number of views: 4291


Let's assume you have installed SQL Server 2005 client tools and the Visual Source Safe client on the same machine.  You're all updated, patched and ready to start some query writing.  Naturally ( it's natural - right? ) you want to have your code in source control.  "Even your queries related to the project?", you may ask.  Yes - even those.

If you open up SQL Management Studio and you don't see the source safe integration there, here is what you do.



First, go into SQL Server Management Studio's "Tools" menu and select "Options..." as shown here.

Options on the Tools menu

Next, open the "Source Control" node of the tree on the left-hand side of the window that opens.  Under it, select the "Plug-in Selection".  The screen should look similar to the one below.

Plug-in Selection

Now click on the "Current source control plug-in" drop down and select ( you guessed it ) "Microsoft Visual SourceSafe" from the list as shown below.

Selecting SourceSafe

Once selected, you should see 2 new items added under the "Source Control" node on the left-hand pane's tree like so.

Selection Complete

Finally "Ok" and close your way back to the main SQL Server Management Studio IDE.  You should be all set.

If you want to customize the way VSS behaves with your project, you may do so under the "Environment" and "Visual SourceSafe" nodes that are added to the options tree.




One thing I did find during this.  If you also have Visual Source Safe 6.0's client installed on the same machine, and you then try to Open Source Safe from SSMS - it seems to "pick" the 6.0 interface instead of the 2005 interface.  I have not dug into why that is yet.  If you happen to know - please leave a comment and a work-around ( and or link ) if you know of one. 

Categories: Blogs
Rate this article:
No rating

Please login or register to post comments.