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»
MonTueWedThuFriSatSun
25262728293031
12345

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!

https://msit.powerbi.com/view?r=eyJrIjoiYTNjNzcwNjctNTczMy00ZDMxLWFlMGUtMDViODA1NGZiNmI0IiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9

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.

Feedback

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


Read more
67
8

MDX NON EMPTY KEYWORD VS NONEMPTY FUNCTION

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.

BOTTOMCOUNT FUNCTION with NON EMPTY Keyword

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.

image

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.

image

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:

image

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
91011121314
15161718192021
22232425262728
29123456

SSIS Denali Resolve References

  • 15 November 2010
  • Author: DevinKnight
  • Number of views: 7678
  • 0 Comments

One of the new features in SSIS Denali that I’m really excited about (Other than the ability to Undo ctrl-z) is the new resolve reference functionality that was brought into the product from the Parallel Data Warehousing team.  Resolve references is solving the problem that occurred when you created a package with a data flow and you made just about any change above your destination.  You would see red x’s on your transforms and to fix the problem you had to try and figure out what the below image was telling you:

If this has ever given you headaches before you will be please to find out with the release of the SQL Server Denali CTP that the resolve references tool will help.  To walk you through this first I’ll demonstrate the problem in the current version of SSIS and then show you how Denali’s resolve references eases the pain.

I have 3 sources as you can see above.  Each source is essentially the same:

·         Source 1 was used to originally configure the data flow. 

·         Source 2 is an exact duplicate of Source 1. 

·         Source 3 is the same but has one of the column names changed.

When you change from one source to another you get the dreaded red x and upon opening the Derived Column the Restore Invalid Column Reference Editor opens as usual.  The same would occur if I connect Source 3.

Resolve reference in Denali makes this easier.  Here’s the same example in Denali:

When I change from Source 1 to Source 2 in SSIS now in Denali it allows this without any problem because the sources are actually exactly the same (as you would hope it would react).

 

When I change to Source 3 I still have the red x problem I had in previous version of SSIS but instead of it being on the transform itself it is now on the data flow path.  This means you can actually fix the reference simply by right click on the path and select Resolve References as shown below.

Upon select the Resolve Reference button it opens a new dialog box that can be used for remapping your columns that have are currently invalid.  Like I mentioned this editor is very similar to the Parallel Data Warehouse adapters for SSIS.  The interface is very nice too.  It’s completely drag and drop to reapply your references as shown below.  When you finish your mapping you click OK and you can result development as normal!

Some other nice features here are:

·         Automap columns based on matching names

·         Filter under each section to find your columns quicker

·         Copy and paste the columns you have selected to be mapped to the clipboard

·         Delete unmapped input columns

·         Preview Changes before you confirm them

Hope this new features gets you as excited as I am about it.  I will try to continue to post new SSIS Denali features as I learn them myself.

Print
Tags:
Rate this article:
5.0
DevinKnight

DevinKnightDevinKnight

Other posts by DevinKnight

Please login or register to post comments.