Progress Data Platform, formerly MarkLogic, is a unified data platform that brings multi-structured data together and curates it for transactional and analytical purposes. The Data Hub ingests data from any source, indexes it for query and search, and curates it.
N/A
SAP BW/4HANA
Score 8.3 out of 10
N/A
SAP BW/4HANA is a next-generation
data warehouse solution. It is specifically designed to use the advanced
in-memory capabilities of the SAP HANA platform. For example, SAP BW/HANA can
integrate many different data sources to provide a single, logical view of all
the data. This could include data contained in SAP and non-SAP applications
running on-premise or in the cloud, and data lakes, such as those contained in
the Apache Hadoop open-source software framework. With SAP BW/4HANA,…
N/A
Vertica Analytics Database
Score 10.0 out of 10
N/A
The Vertica Analytics Platform supplies enterprise data warehouses with big data analytics capabilities and modernization. Vertica was acquired and supported by OpenText, then sold to Rocket Software in 2026.
N/A
Pricing
Progress Data Platform
SAP BW/4HANA
Vertica Analytics Database
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Progress Data Platform
SAP BW/4HANA
Vertica Analytics Database
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
Optional
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Progress Data Platform
SAP BW/4HANA
Vertica Analytics Database
Considered Multiple Products
Progress Data Platform
No answer on this topic
SAP BW/4HANA
Verified User
Anonymous
Chose SAP BW/4HANA
SAP Data services will be mostly useful when we plan to expose the data to non sap world and to the external systems direct integration with BW/4 system is not possible. i feel data services can be an extension to the BW/4HANA which by nature is a default option for any …
we also had oracle based solution for the data lake and it was tedious to build data model with data vaulting concepts. with extended star schema approach in SAP BW/4HANA, it makes the developer life easier to integrate master data attributes and text with the transactional …
We chose SAP BW/4HANA for its out of the box integration and ETL capabilities with our landscape of other SAP solutions in addition to the pre-build SAP delivered business content. Integrated BPC also made it a perfect choice for planning and consolidation in one integrated …
SAP BW / 4HANA and SAP IQ are both used for warehouse; with quick consultations for business analysis and that allows us to obtain dashboards and KPIs efficiently. SAP IQ is columnar and SAP BW / 4HANA immemorial. SAP BW / 4HANA was selected for the response speed of the …
Both are comparable with the advantage going to BW for SAP integration, simplified data modeling, and overall performance. Both play a key part in our overall data warehousing strategy and are complementary based on each of their strengths specific to data provisioning, and …
We use a mix of different tools, primarily Snowflake and SAP BW/4HANA - the first as our main Data Lake and integrated with other reporting and visualization tools, and the second as the main source of BI/Reporting into the ERP layer - Operations, Logistics, Inventory, Finance. …
Unfortunately I never had the chance to work with other tools similar to SAP BW/4HANA. In the different companies I've worked for during the past 4 years, they all used SAP, and in particular I worked in SAP BW during the last year.
We used to have QlikView reporting some years ago. It was very user-friendly but when you needed some kind of data that was not considered by the solution creator, you needed to pay a developer for that need. SAP BW/4HANA needs very little customisation to offer you new data …
SAP Analytics Cloud is complemented by SAP BW/4 HANA through connectors that work in real-time and allow the display of indicator information in interactive and user-friendly visualizations. SAP Data Services integrates with BW/4 HANA allowing to automate the loading of …
Vertica performs well when the query has good stats and is tuned well. Options for GUI clients are ugly and outdated. IO optimized: it's a columnar store with no indexing structures to maintain like traditional databases. The indexing is achieved by storing the data sorted on …
SAP HANA, Oracle, MySQL, and PostgreSQL are too heavyweight for achieving real-time latency requirements. Google BigQuery is limited to Cloud that makes hard to integrate with a large ingestion pipeline that may have both Cloud-based and on-prem components. Hadoop is much more …
MySQL and MS SQL Server are both fantastic RDBMS products. MS SQL Server goes a bit further since it has the builtin analytical functions. But it only scales so far. Once the data goes beyond capacity, getting results out just does not happen anymore. IBM Netezza and …
Presto would be a good solution that would be less expensive and would also allow direct querying of all our data on Hadoop while maintaining good speed.
Vertica is great for small low complex queries and has great query performance over the other technologies that I have worked with. Vertica fails to Hive wrt scalability and resource isolation, where Hive exploits hadoop's resource isolation. Presto is almost comparable to …
Vertica is much easier to manage; is just software (i.e. vs. Netezza), easier to scale and extend, with a very powerful query execution engine and storage layer. While other solutions (e.g. Greenplum) are just postgres clones that were extended to run at scale but still keep …
SAP BW/4HANA is well suited for warehousing solution when majority of the source systems are SAP. With ODP BW and ODP CDS view source system types, SAP standard extractors and CDS view based extractors provides the best support for delta extraction with less lead time for data availability to report. It is less appropriate for the scenarios to do AI/ML use cases for forecasting and predictive scenarios as there are limited options. It is less appropriate for the scenarios to use recent responsive AI tools and LLM.
As someone just starting out with data analytics and warehousing vertica is a great tool for a small scale business. It has amazing performance and can scale upto TBs of data. It works well for any organization which has about 100 - 500 DAUs of the system. The system doesn't require a lot of ops overhead. Scaling for PB data and 1000s of DAU is vertica's weak point. The system is just not designed for large scale usage and still has a long way to go to improve scalability. There are experiments to run Vertica query engine on top of HDFS which seem promising, however - if you have the the Hadoop ecosystem you are better off going the HDFS + Presto/Impala/SparkSQL route. But if you are in the Hadoop ecosystem, you probably are already investing a lot in ops.
Column-oriented storage organization, which increases performance of queries.
Compression, which reduces storage costs and I/O bandwidth. High compression is possible because columns of homogeneous datatypes are stored together and because updates to the main store are batched.
Shared nothing architecture, which reduces system contention for shared resources and allows gradual degradation of performance in the face of hardware failure.
Easy to use and maintain through automated data replication, server recovery, query optimization, and storage optimization.
Support for standard programming interfaces ODBC, JDBC, ADO.NET, and OLEDB.
Integration to Hadoop with the capability to perform analytics on ORC and Parquet files directly.
It would be nice to see tools available within SAP BW/4HANA for cross platform esp. other SAP systems integration from a data extraction and scheduling standpoint. This is to ensure BW data stays consistent with its sources and is refreshed only after completion of core business process activities in its source systems. This is also relevant from a SAC and Datasphere integration standpoint for data being fed from SAP BW/4HANA as these platforms currently only support time based scheduling options with no dependencies possible against SAP BW/4HANA processes. Currently most companies employ an external third party scheduling tool to manage this.
With the advent of Analysis for Office the ability to publish AFO workbooks has been lost directly from the SAP BW/4HANA platform unlike its BEx Analyzer predecessor which had the Broadcaster. The use of BO Platform is not an ideal use case for this functionality which is very basic in its scope.
In this age of AI would be nice to see functionality introduced for AI co-pilots like Joule to speed by data modeling and scheduling activities as well as a natural language based querying options within AFO.
One time, one of the nodes wasn't coming up because of some ambiguity with the local data. Vertica wasn't able to fix it by itself and we were trying to remove the node out of the database and we couldn't do it. It would be great if that could be addressed. Luckily when we rebooted the whole server, some of the dead transaction got flushed because of which vertica was able to recover and the node came up.
SAP BW/4HANA requires specialized skillsets around data warehouse modeling and the access to data, however the modeling capabilities are intuitive and have now become accessible to both SAP and non-SAP data warehouse specialists. This new model allows for Interchangeable skillsets and access to a broader pool of experts throughout the industry, as well as easier access to data.
I never experienced any support issue when using SAP BW/4HANA. The only issues I faced were at the moment of installing the tool in my computer but I got support from the local IT department of my company and was quickly fixed
HP/Micro Focus Vertica support is in par with other bigger vendors. In addition to this, there is enough best practices documentation available for some of the most common ways you will use Vertica that makes it easy to get Vertica up and running.
We chose SAP BW/4HANA for its out of the box integration and ETL capabilities with our landscape of other SAP solutions in addition to the pre-build SAP delivered business content. Integrated BPC also made it a perfect choice for planning and consolidation in one integrated environment. Qlik and Power BI were primarily used as additional visualization tools for business users with data integration against SAP BW/4HANA as opposed to being used as a full blown data warehousing platform. This was however before the introduction of SAP Analytics Cloud.
MySQL and MS SQL Server are both fantastic RDBMS products. MS SQL Server goes a bit further since it has the builtin analytical functions. But it only scales so far. Once the data goes beyond capacity, getting results out just does not happen anymore. IBM Netezza and Teradata were both appliances that required different expertise than we had in house. Vertica was able to do the same, and in some cases better, on commodity hardware (frankly in our case old servers that were slated for recycling!) and at a small scale. In other words, Vertica we could grow slowly over time. Infobright is a great log processing database but for the functions we were looking to serve it just didn't have some of the features Vertica had that we felt were show stoppers.
Still acting as important point of source for major decisions
After BW/4HANA Migration there is 20 % increase in the extractions to BW system
Still we are yet to find a better investment for reporting in SAP , though we use SAC, which has its own issues while dealing with huge volumes of data