We performed a comparison between Kovair Data Lake and SAP BW4HANA based on real PeerSpot user reviews.
Find out in this report how the two Data Warehouse solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The tool's most valuable features for us are its combination of formatting, ETL, analytics, and storage capabilities."
"The most valuable feature is the ability to interact with teachers in real-time and manage lessons after class."
"The most valuable feature is that we can transform a huge amount of data and apply business logic as per the requirements."
"The most valuable feature is that it's robust."
"The UI is completely new, beautiful, and user-friendly. There are some other helpful features like global filters and advanced tools. We can perform custom calculations easily From a technical perspective, the performance has been enhanced and optimized for a limited number of flows. The content settings are more advanced, and there are so many other features that I can't name them all."
"The solution is useful for connecting with external systems."
"Provides a great analytics engine with all the capabilities."
"The solution is based on SAP ERP, so there's some business content already included. For customers who use SAP ERP, SAP BW4HANA is a good choice for their DW implementation."
"The processes are the most valuable aspect of this solution."
"The solution's performance is really good. Also, it's easy to operate, easy to administer, and relatively simple to install."
"Maybe the chat conversation feature could be improved."
"The solution is expensive. For future releases, it would be beneficial if Kovair Data Lake could enhance its ETL and data capabilities."
"They have taken out a few BW functionalities when they redesigned this. The way of multi-dimensional thinking and star schema got a little bit lost. It may be because of the cost, but certain functionalities that were previously implemented from the BW side should come back again in the whole product. It is a young product. It is version 2.0. In time, I'm pretty sure they will come back again because otherwise, it limits the potential of the product, and I have to do a lot of modeling towards that direction. For me, the analytics focus is too much. It is not cube-oriented in that way, so its functionality is limited. It is not really technically limited in the back end; it is more limited in the front end. It has a data-mining mindset for SQL developers. The navigational attributes should be easy. It needs to be built in models. I see the data mark cube or understanding that the composite provider needs to be models in a cube coming back. The multi-dimensional star schema approach and the reporting need to be done as well as possible to leverage the star scheme below. This is definitely not understood by many consultants and even composite providers for star schema. They always think in terms of flat tables, which is limiting. You need to build the right dimensions, objects, and so on. If you can build this in BW4HANA, then you have this understanding that BW4HANA is not forcing you in this direction, but it should force you a bit better in this direction. Maybe a few elements which were in use in BW should come back again. It would help the community to determine the direction to build on the cube. You can have maybe 50 elements, and then you can expand it to what you need by leveraging navigation. So far, this functionality is a little bit limited in the tool, and it is not thought through, but I think it will come. They should also be adding more capabilities for the transformation between different objects. In BW, this is currently limited, especially towards composite providers. It is a bit complex basically in the building. You have to have a lot of knowledge as well as know how to do it better because it is a bit different from BW. There is not too much expertise currently in the consulting markets. Many are trying to build something, but it may be based on their knowledge of what they have from the BW and HANA side. You have to find the right mix from both of them at this time. We also have HANA Native. These are our two different sync sources basically, and we have approaches to connect nicely, but it is hard to manage your team because a lot of coaching is required."
"BW/4HANA could improve query optimization. For example, there could be an error message that pops up when you hover over it if any query fails. That would make it easier to find out what went gone wrong. Guided SAP help tools would make it easier for us to go forward."
"The tool is not cloud-compatible."
"The tool is not easy to use for an end user."
"I would like to be able to design new reports in a future release."
"The monitoring for the remodeling feature is very difficult to understand."
"It takes too long to escalate problems from the first level of support."
"From a technical perspective, it could be even more related to legacy systems. The connectivity requirement is quite high and requires systems that are up-to-date."
Kovair Data Lake is ranked 18th in Data Warehouse with 2 reviews while SAP BW4HANA is ranked 7th in Data Warehouse with 33 reviews. Kovair Data Lake is rated 8.0, while SAP BW4HANA is rated 7.4. The top reviewer of Kovair Data Lake writes "Ability to interact with teachers in real-time and manage lessons after class". On the other hand, the top reviewer of SAP BW4HANA writes "An easy-to-operate and administer tool that needs to consider revising its existing licensing cost". Kovair Data Lake is most compared with Oracle Exadata, whereas SAP BW4HANA is most compared with Microsoft Azure Synapse Analytics, Snowflake, Amazon Redshift, SAP HANA and SQL Server. See our Kovair Data Lake vs. SAP BW4HANA report.
See our list of best Data Warehouse vendors.
We monitor all Data Warehouse 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.