Databricks Data Intelligence Platform vs. Microsoft BI (MSBI)

Medium to Large data throughput shops will benefit the most from Databricks Spark processing. Smaller use cases may find the barrier to entry a bit too high for casual use cases. Some of the overhead to kicking off a Spark compute job can actually lead to your workloads taking longer, but past a certain point the performance returns cannot be beat.

Incentivized

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.

• Process raw data in One Lake (S3) env to relational tables and views
• Share notebooks with our business analysts so that they can use the queries and generate value out of the data
• Try out PySpark and Spark SQL queries on raw data before using them in our Spark jobs
• Modern day ETL operations made easy using Databricks. Provide access mechanism for different set of customers

Incentivized

• Comparatively easy to use compared to other data analytics solutions, collaborating with other colleagues on data work is simple.
• Using Visual Studio for database, ETL, reporting, and analytics development save time and money.
• Transfer of data from one application to another via Excel and comparison of data attributes between applications
• Dashboard functionality, as well as Python support, are available, allowing you to add additional charts and graphs.

Incentivized

• Connect my local code in Visual code to my Databricks Lakehouse Platform cluster so I can run the code on the cluster. The old databricks-connect approach has many bugs and is hard to set up. The new Databricks Lakehouse Platform extension on Visual Code, doesn't allow the developers to debug their code line by line (only we can run the code).
• Maybe have a specific Databricks Lakehouse Platform IDE that can be used by Databricks Lakehouse Platform users to develop locally.
• Visualization in MLFLOW experiment can be enhanced

Incentivized

• 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

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.

Because it is an amazing platform for designing experiments and delivering a deep dive analysis that requires execution of highly complex queries, as well as it allows to share the information and insights across the company with their shared workspaces, while keeping it secured.

in terms of graph generation and interaction it could improve their UI and UX

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

The product has been reliable.

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.

One of the best customer and technology support that I have ever experienced in my career. You pay for what you get and you get the Rolls Royce. It reminds me of the customer support of SAS in the 2000s when the tools were reaching some limits and their engineer wanted to know more about what we were doing, long before "data science" was even a name. Databricks truly embraces the partnership with their customer and help them on any given challenge.

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.

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.

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.

The most important differentiating factor for Databricks Lakehouse Platform from these other platforms is support for ACID transactions and the time travel feature. Also, native integration with managed MLflow is a plus. EMR, Cloudera, and Hortonworks are not as optimized when it comes to Spark Job Execution. Other platforms need to be self-managed, which is another huge hassle.

Incentivized

We have used the built in ConnectWise Manager reports and custom reports. The reports provide static data. PowerBI shows us live data we can drill down into and easily adjust parameters. It's much more useful than a static PDF report.

Incentivized

• The ability to spin up a BIG Data platform with little infrastructure overhead allows us to focus on business value not admin
• DB has the ability to terminate/time out instances which helps manage cost.
• The ability to quickly access typical hard to build data scenarios easily is a strength.

Incentivized

• As a SaaS provider we see being able to provide self-service BI to our client users as a competitive advantage. In fact the MSSQL enabled BI is a contributing factor to many winning RFPs we have done for prospective client organisations.
• However MSSQL BI requires extensive knowledge and skills to design and develop data warehouses & data models as a foundation to support business analysts and users to interrogate data effectively and efficiently. Often times we find having strong in-house MSSQL expertise is a bless.

Incentivized