Microsoft BI (MSBI) vs. Pentaho

Microsoft BI is well suited for Stream analytics, easy data integration, report creation and UI/UX designs (limited but what all available are great ones) Microsoft BI may be less appropriate for handling huge number of datasets and difficult queries. It may also be difficult for a company with heavy data.

Pentaho is very well suited to perform data extraction & data mining from various cloud storage & transform that data using various available data models. However, the software struggles when it comes to visualizing the extracted data in an appealing manner & can be difficult for end-users to get an understanding of data tables created using those models.

Incentivized

• The layout of Power BI is very intuitive. Someone that is familiar with Excel and working with Charts and Graphs in that environment will find the learning curve a rather short one to start using Power BI.
• I like the way Power BI fits an assortment of users and how the functionality that you engage is replicated in Excel, that being Power Query and Power Pivot. So what you learn in one tool can be readily applied towards the other which allows you to more effectively apply your training.
• I appreciate how Microsoft is working to develop tools that go a long ways to empowering the end user. Prior to Power BI I would have had to consult with a "BI" professional to develop a dashboard. With Power BI I don't have to consult with anyone, I can work to put together the dash board I want and using a tool set that is really robust and allows me to engage an enormous amount of data. It's provides a great deal of flexibility and the types of data I can connect to.
• Updates...Microsoft is working diligently to keep Power BI current with monthly updates. They do a really good job of listening to the end user, if there is functionality not currently present just give them a month or so.
• Just to be clear, even though it's easy to get going right out of the gate with Power BI it provides plenty of opportunities to create some really sophisticated reporting solutions. With DAX in Power Pivot and M language in Power Query, you are provided with plenty of head room to do some really amazing things in Power BI.
• Training...there are resources across the web for learning and growing your skills and Power BI. And what's even better is the majority of those resources are free.
• Data engagement, when presenting the data to the end user Power BI goes a long way to allowing that end user to engage the data and begin to identify root cause by simply interacting with the graph/chart/data set. It allows for really fluid engagement. Prior to Power BI so many times during the presentation of data we often times ended the engagement with that data with more questions than what were answered. With Power BI, more often than not, the end user is able to get answers to the questions by simply clicking on the data in the graph/chart/dataset to see the details. This tool really does have the capacity to make you look like a rock star.

Incentivized

• Integrate and synchronize with big data easily
• Import data from any sources and different databases
• Managing data in on-premise, hybrid and cloud environments.
• Compatibility and flexibility of the platform with any type of scenario and any business or industry
• Various tools in the software suite to transformation of data
• Simple interface appearance and creative UI graphics

• The race to perfect gathering of Non-Traditional datasets is on-going; with Microsoft arguably not the leader of the pack in this category.
• Licensing options for PowerBI visualizations may be a factor. I.e. if you need to implement B2C PowerBI visualizations, the cost is considerably high especially for startups.
• Some clients are still resistant putting their data on the cloud, which restricts lots of functionality to Power BI.

Incentivized

• I think the relative obscurity of the tool is a downside, not as many developers, consultants or peers you can tap into.
• Lack of a solid user community held us back, looking at Power BI and Qlik, they have huge user communities that help each other out. Would have liked that here.
• Smaller company means smaller sales force, and the lack of a local presence made it hard to only interact online with the account rep. Other companies have someone local who often stops by with pre-sales developers to just pitch in free of charge when they have time.

Incentivized

Microsoft BI is fundamental to our suite of BI applications. That being said, Northcraft Analytics is focused on delighting our customers, so if the underlying factors of our decision change, we would choose to re-write our BI applications on a different stack. Luckily, mathematics are the fundamental IP of our technology... and is portable across all BI platforms for the foreseeable future.

I will use Pentaho until I find a better tool with a better, easier to use report designer client. For now, Pentaho has been the most powerful reporting tool for our clients because of its ability to connect to Odoo, integrate in Odoo (reports are accessible in Odoo) and the flexibility in report design and parameter integration

Incentivized

The Microsoft BI tools have great usability for both developers and end users alike. For developers familiar with Visual Studio, there is little learning curve. For those not, the single Visual Studio IDE means not having to learn separate tools for each component. For end-users, the web interface for SSRS is simple to navigate with intuitive controls. For ad-hoc analysis, Excel can connect directly to SSAS and provide a pivot table like experience which is familiar to many users. For database development, there is beginning to be some confusion, as there are now three tool choices (VS, SSMS, Azure Data Studio) for developers. I would like to see Azure Data Studio become the superset of SSMS and eventually supplant it.

Incentivized

Even if Pentaho requires less technical skills to develop a pipeline or ETL project, its learning curve can be a bit slow since there are many ways to do the same thing as in any other platform. However, in Pentaho, some things can be confusing some moments for non-technical teams.

Incentivized

Reports are stable and always avaiable when needed.

SQL Server Reporting Services (SSRS) can drag at times. We created two report servers and placed them under an F5 load balancer. This configuration has worked well. We have seen sluggish performance at times due to the Windows Firewall.

While support from Microsoft isn't necessarily always best of breed, you're also not paying the price for premium support that you would on other platforms. The strength of the stack is in the ecosystem that surrounds it. In contrast to other products, there are hundreds, even thousands of bloggers that post daily as well as vibrant user communities that surround the tool. I've had much better luck finding help with SQL Server related issues than I have with any other product, but that help doesn't always come directly from Microsoft.

We are an Enterprise customer. They handle problems INSTANTLY when they are critical, including initiation an immediate WebEx screen share call when needed. Smaller/less-critical problems are handled within 1-2 days -- and NEVER fall off their radar, no matter how small. As needed, we can also leverage "professional services" from them -- much of which is included in our Enterprise contract. Finally, when a problem I have discovered turns out to be a bug..they create a JIRA for the fix, and make me a watcher. I love seeing notes come in showing me status updates of bugs filed because of something I found. They really are TOP-NOTCH.

This training was more directed toward what the product was capable of rather than actual programming.

I have used on-line training from Microsoft and from Pragmatic Works. I would recommend Pragmatic Works as the best way to get up to speed quickly, and then use the Microsoft on-line training to deep dive into specific features that you need to get depth with.

Course Taken: DI1000 Pentaho Data Integration Fundamentals Setup A week before your class started, the instructor will start sending out class material and lab setup instructions. This is helpful so that you understand how the environment is laid out and can start reviewing the content. Ultimately it saved about a 1/2 day trying to setup with 10 other people online which was great! The Course The 3-day course was laid out like many other technical classes with 15-30 minutes instruction and 15-60 minutes of lab exercises. The instructor was very knowledgeable with the functionality from version to version and answered questions as we went along. I was amazed at some of the functionality that was available that I was not using at the time and quickly implemented changes to many existing transformations and jobs. The novice users seemed to catch on quickly and more experienced users explained how some of the functionality was used in their home environments. Towards the end there was enough time so that we were able to ask very directed questions about our own environments. Overall, I really found the class to be informative and deliver enough information to be dangerous. My skills improved and I was able to design better and efficient transformations for the HIE. Course Description: https://training.pentaho.com/instructor-led-training/pentaho-data-integration-fundamentals-di1000

We are a consulting firm and as such our best resources are always billing on client projects. Our internal implementation has weaknesses, but that's true for any company like ours. My rating is based on the product's ease of implementation.

Get the right people in before starting implementation. Start small and build as you go approach is time consuming and involves lot of rework. Evangalize within the organization the capabilities and limitations equally so that correct delivery expectations are set. Set expectations with the Customer that the tool cannot replace proprietary software in terms of stability/usability and that timelines could change given the new ness of the product.

Incentivized

We use Microsoft BI because our organization has all of its software in the Microsoft ecosystem. It just made sense to utilize Microsoft BI because it can so seamlessly connect to all of the other Microsoft tools and data sources that we were using before. We often find that more people have experience with Microsoft BI than other tools that we looked at due to its popularity and widespread use within other organizations.

Incentivized

Perhaps Snowflake and SalesForce have some components which align with the Pentaho tools. The Pentaho tools have integrations with these technologies to add more value to the final users. Perhaps the only weakness I can honestly find in the Pentaho tools right now is the lack of a powerful web interface for data transformations. There is a web component from which you can access existing data transformations created with the Pentaho Data Integration tool. Still, the web component only allows visualization of the data transformation and remote execution. A complete web interface with remote execution would be excellent, and I'm sure that we might see something like this available at some point in the future.

Incentivized

• Profit increase due to MSBI output and a better understanding of multiple functions other than cost.
• Data compatibility will be improved, and MSBI will have the opportunity to handle the API more effectively. The MSBI ETL stack works well with relational databases, but with cloud-based data sources emerging, non-relational data sources should be supported.
• Save time interpreting data. Our analytics capabilities have helped our clients understand complex data with simple reports. Thus, it facilitated decision-making.

Incentivized

• Pentaho has improved our overall business process.
• Pentaho has helped the Managers and Directors to analyze the numbers going up and down from time to time.
• We have a started a big project using Pentaho that is going to include all the business processes in the organization.

Incentivized