So you’ve decided or perhaps were told to do a technical presentation. If this is something that’s new for you, then you may be going through a variety of emotions. You may start feeling excited in anticipation of the event, but often that quickly that changes to anxiety as you realize the amount ofwork ahead of you. As an experienced technical presenter, I understand what you're going through and the challenges you'll face throughout the process.
**Information is current as of 5/21/2015**
Recently Azure SQL Database was added as a new connection to the Power BI Preview. Read the notes about how it can be used here. The things I found especially worth noting were:
Have you ever had a user run a query against one of your largest tables only for them to immediately filter the results in Excel to show the last years worth of data? All of that data brought across your network and then immediately filtered out. Or maybe Excel just can handle the amount of unfiltered data they’re trying to return.
If you’ve have used or even just seen a demo of Power BI Q&A you’ve likely seen there’s great potential in the feature for even low-tech user. I usually say, “If the user knows how to use a search engine then they can interact with Q&A.” You can read the basics of how Power BI Q&A works from my previous post here.
While having this capability is great it can take some fine tuning to perfect for users interacting with it. Power BI provides you with the ability to now optimize your models for Q&A and it can all be done directly from the Power BI site with what Microsoft is callingCloud Modeling.
By: Devin Knight
Writing MDX inside of Reporting Services has been the nemesis for many report writers for far too long. If all you need is the Query Designer to create a drag and drop datasets then it’s a piece of cake, but have you ever wondered what’s going on with all the MDX that the Query Designer creates. Or how about how do the parameters work that it creates inside MDX. I’ve heard many report writers that use Analysis Services as a data source (including myself) say it is too difficult to create parameters and that’s why they use the Query Designer.