We performed a comparison between Microsoft Power BI and SQL Server based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Tableau, Oracle and others in BI (Business Intelligence) Tools."Previously we used Excel, which took a long time - two or three weeks - to bring the data into a uniform format, whereas BI can do the same job in a day."
"It is stable enough. It has a lot of powerful functions. It can also be customized with the DAX language. It is also intuitive enough and incremental. You can start with something simple, and then step-by-step, you can increase the reports and dashboards according to your needs."
"What I like most is that I can do everything in Power BI that I can do in Excel."
"This solution has improved our ability in making decisions and explaining data."
"The ease of integration and connectivity stands out as the most critical aspect, followed closely by the flexibility to customize reports and dashboards."
"MS SQL & SQL Server Analysis Services."
"Data integration is very useful in Power BI. It lets me collect data from many sources. For example, I can get data from Oracle databases and SQL Server databases at the same time."
"In my experience the scalability is good. You are able to increase users and add more data."
"SQL Server is an inexpensive solution. I recommend it if the project isn't sensitive. SQL is similar to Oracle and integrates well with tools in the cloud environment. The difference is that Oracle is for data solutions where there is replication and moderation."
"Without any doubt the Integration Services and Analysis Services are the most widely used. These are the basis for data quality, data gathering, ETL process, as well as collation for the data warehouse, Cube-generation, and ad-hoc processes. The ease in which you may mold a process flow or even modularly add in new structures is something which is much needed in my job."
"The initial setup isn't overly complex."
"The Always On tool improves the SQL server availability."
"SQL is very easy to manage."
"The solution has proven to be very stable."
"The scalability is very good."
"It works fine in terms of performance and stability."
"Power BI doesn't support some open-source data sources that are new, such as SnowSQL, Iceberg, or ClickHouse."
"The solution could improve by simplifying the user interface and adding integration or compatibility with APA."
"They can improve the user interface a little bit to make it more user-friendly. When creating a dashboard, it is not very user-friendly. You have to click on a certain style and use your keyboard keys to move it. You cannot drag and drop it."
"Not having to login again after a mobile app upgrade. A simple login on mobile would be great."
"From a scalability and performance perspective and based on my understanding and feedback from end users, there's room for improvement in data processing, scaling up, and leveraging the cloud. That could be an enhancement area for me to look into."
"There are certain features that are only available in the cloud version. It would be beneficial if they could be brought down to the on-premise version without the necessity of using the enterprise SQL database, as that can be very costly. We need more cost-effective features that are available in the cloud to be accessible on-premise."
"Integrating it with the physics build model or the engineering model should be included."
"Integration with products that are not Microsoft could be more improved."
"The performance could improve."
"When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that."
"There is room for improvement in terms of pricing for SQL Server."
"The integration could be better. They are not open-source, so the integration with other platforms is not that easy."
"The installation process should be simplified."
"The stability of the solution should be improved in the next release. Sometimes it is great, sometimes it is troublesome. I would also like data conversion and the code pages to be a bit more straightforward."
"Performance could be better. But I don't know if it's a problem with my application or with my database."
"The ability to connect with other environments needs to be improved."
Microsoft Power BI is ranked 1st in BI (Business Intelligence) Tools with 297 reviews while SQL Server is ranked 1st in Relational Databases Tools with 260 reviews. Microsoft Power BI is rated 8.0, while SQL Server is rated 8.4. The top reviewer of Microsoft Power BI writes "A complete ecosystem with an builtin ETL tool, good integrations with python and R, and support of DAX and Power Query (M languages)". On the other hand, the top reviewer of SQL Server writes "Easy to use and provides good speed and data recovery". Microsoft Power BI is most compared with Tableau, Amazon QuickSight, KNIME, Domo and Oracle OBIEE, whereas SQL Server is most compared with MariaDB, SAP HANA, Oracle Database, LocalDB and IBM Db2 Database.
We monitor all BI (Business Intelligence) Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.