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

Does the Cloud Mark the End of the Production DBA?

  • 1 July 2011
  • Author: Brian Knight
  • Number of views: 1023
  • 0 Comments

While I’ve been on the Expedition Denali roadshow, a portion of the event is about SQL Azure, Microsoft’s new cloud database computing platform. I always enjoy watching and surveying the DBAs in the audience during and after the session about how they feel this is going to affect their jobs. Microsoft has been pitching Azure as a fundamental shift in the way we manage and store data, pushing the onus of managing the database, patches and operating systems to Microsoft. Reading between the lines, does that mean this will cost DBAs their jobs?

Before you get concerned if you’re reading this you must first consider the adoption rates of Azure, which has been more targeted at small to medium businesses, who typically don’t have a DBA staff on board. The present SQL Azure platform has a limit of 50GB per database, which prohibits data loads outside the new-medium sized database. There is also a cost issue, which is steep for many companies. When Pragmatic Works looked at Azure for our internal business, our BIDN database was going to be close to $500/month plus usage fees on top of that. In our example, the ROI wasn’t there, since our database only costs us a fraction of our time to manage.

If you’re a DBA, you have nothing to fear but you should start making tweaks to your resume. If you’re a production-only DBA for example, you must become a specialist on VLDB (very large databases) or how to manage databases more effectively. I think you’ll see over the next decade a fundamental shift for DBAs where we go into two camps: one that manages multi-terrabyte databases and another that manages hundreds of smaller databases across the company very efficiently.

During the recession, business intelligence projects were some of the only projects that had double-digit growth. This is because companies were trying to become more productive and get a leg-up on their competition. This spurred the growth of multi-terrabyte databases and cubes. We have several customers that now have data warehouses crossing 10s of terrabytes. Having this size of a database triggers a new style of database administrator. For example, backing up a database that’s 10TB, can’t be done the traditional way.

With this type of new data load on servers, we’re also seeing very specialized appliances out like the PDW and Fast Track architectures. This BI architecture depends on sub-second response time from server to end-user. This type of demand and experience is not possible in the cloud. DBAs that specialize in delivering this type of response time to the end user will become even more of a commodity but they must get their hands dirty and think outside of the box to accomplish this.

Many companies have also seen a huge explosion of smaller databases as more of their world becomes electronic. Much of this is from 3rd party applications that have been installed and the other part from small internal databases. While this load may make sense for the cloud, the ROI will not be there when a company has hundreds of databases that could be consolidated onto just one or two servers.

If you believe the cloud DB store or not, things are going to change over the next decade. You will see some dip their toes into the cloud and some will have success doing so. This will remain a small to medium databases with lower SLAs for performance. So, the DBA job will change over the next decade but it will still remain strong.

 

 

Print
Categories: Blogs
Rate this article:
No rating
Brian Knight

Brian KnightBrian Knight

Other posts by Brian Knight

Please login or register to post comments.