Voice of the DBA

Tag: Power BI

  • Data Science, BI, and Reports

    Data science, along with the Artificial Intelligence (AI) and Machine Learning (ML) fields, is often seen as the new direction in which we ought to move our analysis of all the bits and bytes that we collect and store in our databases. There is so much hype now about those technologies, and managers are buying in.

    I’m not sure I agree. I do think that AI and ML will increasingly be used, but they’re just a part of what you use to analyze data. Buck Woody has a good post about the way in which we might examine our technology stacks used for BI work.

    We have a lot of reporting technologies to enable us to make better decisions, and there is a space for all of them. Many people like Excel, some use tools like Power BI and Tableau, still others prefer to get insight boiled down to a single number that influences them to move one way or the other.

    There is a lot being written about AI and ML technologies and certainly many organizations experimenting with them. Data Ccience covers these areas and more, asking our data not just what it says, but potentially what this might mean in the future.

    However, this doesn’t replace traditional BI and reporting. As Buck notes, these are tools and you should use the ones that work for your organization. Learn about them, experiment, understand the impact they have on your audience, and choose the best tools for the job.

    I’m sure this area will continue to evolve, and we’ll get new tools and techniques to help organizations make better decisions. Whether this will actually improve forecasting is likely up to the skills of both the technical and business people.

    Steve Jones

  • Microsoft, Think DevOps First

    This post from Melissa Coates is a good example of not thinking through your product architecture early on. The short version of the post is that Power Bi Desktop is a better place, perhaps really the only place, to author your Power BI Reports. Melissa covers a few potential issues while using the Power BI online editor, but the big item is that you cannot easily prevent conflicts and track versions there.

    Power BI started as the online service, with the Power BI Desktop tool seeming like a bit of an afterthought. At least from the marketing perspective as all of the early demos and media from Microsoft was about the online report service. Since then it’s evolved to become the primary way we will build reports in SQL Server moving forward, which I think is a good move.

    While I can understand the developers at Microsoft not really thinking that the service would on-premises and maybe not considering the need to provide some text format for the reports, I can’t understand why they didn’t learn from the Integration Services team and realize that binary versions of programmable items don’t make sense. We need a format that can be easily versioned, and maybe more importantly, stored in a VCS and diff’d in a way humans can understand.

    When building a format for storing code, please consider the need to work in a team and version the changes made. This means any format should not be a) binary and b) difficult to decode. Separate visual elements from logical elements and ensure a text version of this can be examined by developers. You can use XML, JSON, YAML, or any other text based format, but choose something that makes sense. Even if you add your own extension, ensure that standard tools that work with code can use this.

    I do know the PBIX format is a ZIP file, but zip files don’t easily integrate with a VCS. We could use hooks to extract/rebuild out files on commit/checkout, but that’s cumbersome and silly. I’d rather that the PBIX were a folder with the files inside. Users, including my Mom, can zip a folder and email that if needed. To me, that would have been a better structure from the beginning.

    Microsoft is supposed to be a company providing platforms that we build upon and use in our work. The decisions for the Power BI service seem to be poorly thought through with that in mind. I’d urge them to create a baseline set of rules for future products that consider DevOps, teams, and the need to track code.

    Steve Jones

  • Power BI Desktop on the Mac

    Power Bi is one of the neatest tools that Microsoft has built for data professionals. It allows anyone to build fantastic interactive visualizations that can help tell a story and help someone make decisions. There have been some amazing demo visualizations from Microsoft customers. I’ve seen a predictive maintenance visualization for airplanes, one for diabetes trends and a fun basketball visual. There are also a fantastic set of custom visual controls, quite a few of which are described in Devin Knights blog series.

    If you don’t know anything about Power BI, there are lots of resources, including some amazing tips from the Guy in a Cube. Adam Saxton has an amazing channel and puts together some impressive videos with Patrick LeBlanc. They might be one of the best sources for learning to work with the tools. You might want to spend some time playing with Power BI as I can almost guarantee that you’ll build better reports with this tool than you would otherwise. You’ll impress your customers, clients, and boss with your design work.

    Plenty of people have Mac laptops, especially business people, and for quite some time they’ve had to deal with a lack of native tooling. Certainly there are lots of software ports, and no shortage of web software, but there are always places where a lack of a native solution is problematic. I don’t know that we’ll get lots of software ported to a new OS, but there is a better solution. Containerization can help smooth the way.

    A few years back I met the Kenji Obata, founder of Turbo.net. He was doing some interesting work with containers, and I was fascinated by their work. Since then, they’ve grown and refined their technology, and now they have Power BI for Mac available. As soon as I saw their walk-through video, I wanted to share the experience. It’s pretty amazing, and if I were still running OSX, I’d be looking to use some of the Microsoft tools I want on the native desktop.

    This isn’t really native, but the experience feels native. The use of containerization technology might be debatable for databases, but for client applications, it’s amazing. The way that Turbo.net packages up applications is incredible. I like Turbo, and if you need to use Microsoft client applications on a Mac, you might give them a try. It’s not free, but it’s way better than virtualization and has some really cool features as well. I’m sure lots of non-technical people, especially management, that might build reports would love the experience of running Power Bi Desktop on their Mac.

    They even have SSMS available as a turbo container for the Mac, if you’re interested.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 4.6MB) podcast or subscribe to the feed at iTunes and Libsyn.

  • The Power BI Pivot

    This week we had quite a bit of Power BI content appear on various blogs and sites. Some of this was normal traffic, with Power BI gaining popularity and more data professionals writing about the topic. There are always quite a few blogs from The Guy in a Cube, including a look at how to better use colors, but I also see more and more posts from others. We had others about R in Power BI and custom visuals.

    The big news this week was the announcement of the Power BI Report Server from Microsoft. This is coming late in the second quarter of 2017, according to the SSRS blog, which I assume means in the next month. The second quarter is almost over, and with Microsoft ending their fiscal year in June, I’d expect this to release sooner than later. There is also a Power BI Premium, which apparently allows an enterprise to purchase capacity in the cloud and then concurrently deploy Power BI reports on-premises.

    Many people have been looking forward to this. I’ve been hearing from some reporting authors that we were going to get Power BI rolled into SSRS as an option for SQL reporting. Apparently we are, but there are some new costs here. This may change your calculation of whether this is a good move for your organization, but certainly I think that Power BI is one of the better reporting engines I’ve seen.

    The licensing is confusing, and I liked in a few other thoughts on the announcement from others, such as Dan English and James Serra. Both note that the free tier gets to connect to the same data sources as the Pro previously could (including on premises data), which is good. The storage quota increases to 10GB, up to 8 refreshes a day and a bit more. Pro is still $10/month, and apparently is still needed for those that spend the money on Premium if they author reports or export to Excel, even if you have Enterprise Edition. At least, that’s what Mr. English notes in the license terms. Alternatively you can spend a few thousand dollars a month for the cloud version and let all your employees access reports in the cloud or from a local report server.

    Power BI has been one of those amazing products that I’ve been very impressed with in the technical sense. I can build amazing reports, and get great interactivity, allowing me to analyze data in a way that hasn’t always been possible in a visual tool. Almost every time I see a new type of report or some demo, I’m impressed with what’s possible. I love the desktop tool for my own use, since it’s a nice, responsive and easy to understand interface. However the deployment method (originally just with PowerBI.com) and the licensing have always struck me as a bit strange, and perhaps somewhat crippled. It certainly felt that many features didn’t cost me money directly, but there was a cost. With this latest change, it feels like another pivot to try and increase revenue, but not in a way that’s attractive to me.

    Microsoft wants to make money, and they’ve certainly invested money in the Power BI platform, so they get to make the rules. I do like Power BI, and if the costs make sense to you, and there’s enough value, this is certainly a very powerful visualization and reporting tool that I can only imagine will become more and more useful over time.

    Steve Jones