We performed a comparison between SAP IQ, SQL Server, and Vertica based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Oracle, SAP and others in Relational Databases Tools."Valuable features for us include the compression, speed, fast response time, and easy object maintenance."
"It is very robust for ad hoc DW queries and its columnar compression is unique and valuable."
"The primary benefit of SAP IQ is its ability to limit the expansion of the costly SAP HANA database, which has limited storage capacity. This necessitates a form of data management that involves moving data from SAP HANA to SAP NLS, which is essentially archiving. This allows us to retain access to the data via a link whenever it is required."
"Columnar storage allows high compression, high load rates and high query performance."
"The column-based technologies (basically all the database for ITP) are used for SAP IQ. It is used as a column-based solution."
"Unbeatable speed and compression with a colummn-structured relational database."
"I have seen that this is a very stable product."
"We have many users, between 50 and 100 using the SQL Server product."
"I like the availability group functionality. We are setting up more clusters using availability groups. The enterprise licensing or Software Assurance makes it a little bit cheaper as well. It is nice to have that read-only copy for reporting and everything else."
"It is easy to use and easy to perform a backup."
"A big advantage is the ability to store any type of data in SQL Server."
"The replication feature, user interface, reporting services, and notification services are really good. They are providing SQL profiler and SQLCMD as their integrated software, so we don't find it difficult to integrate any of our third-party applications with MS SQL because all of them support MS SQL very clearly."
"You could have an offsite and an onsite, and if the onsite goes down, the offsite picks it up. I like that flexibility to provide continuing operations."
"The stability is fine, especially if you're hosting it on AWS or Azure. You can get up to 99.99% stability on AWS."
"The performance is very good and the aggregate records are fast."
"We are able to integrate our Vertica data warehouse with Tableau to create numerous reports quickly and efficiently."
"It maximize cloud economics for mission-critical big data analytical initiatives."
"Vertica is a great product because customers can compress and code data. The infrastructure that data warehouse solutions need is a commodity server so that customers don't have to invest in infrastructure."
"We are also opening new areas of business and potential new revenue streams using Vertica's analytic functions, most notably geospatial, where we are able to run billions of comparisons of lat/long point locations against polygon and point/radius locations in seconds. "
"Vertica has a few features that I like. From an architecture standpoint, they have separated compute and storage. So you have low-cost object storage for primary storage and the ability to have several sub-clusters working off the same ObjectStore. So it provides workload isolation."
"Eighty percent of the ETL operations have improved since implementing this solution."
"The most valuable feature of Vertica is the ability to receive large aggregations at a very quick pace. The use case of subclusters is very good."
"I think the universe should be part of the Sybase IQ tool set."
"Multiplex is very problematic. There are consistency problems in the metadata, meaning it is possible to lose metadata consistency. You should make sure you have healthy backups."
"The organization who owns the product does not support it well and appears not to be doing significant development for the future."
"The room for improvement would be the marketing of the product, because this product is much better than advertised."
"Concurrency and functional error messaging."
"The solution works best when combined with other SAP solutions. If the environment has other systems other options might be better."
"Its support for JSON should be improved. It does support JSON, but the support is not good enough currently. They should also improve the way indexes work. Its performance can also be improved because sometimes it becomes very slow for certain table designs. It cannot have more than a certain amount of data. As compared to other databases, its capability to handle large volumes of data is not very good."
"With so much data, things can get slow, which is why I would like to be able to understand how to better optimize queries."
"SQL Server could improve the integration with nonrational database solutions, such as MongoDB."
"I would like to see the database become fully automated."
"I would like to see SQL Server add the ability to write to multiple sites or support replication between multiple sites at the transaction level."
"I would like Microsoft to evolve SQL Server because stateful databases dying are in a way. We would like to find out if it can absorb Hadoop and other similar things. They should make it useful for data mining. Data is evolving forever, and how we store it is also changing constantly. So, SQL Server also needs to change."
"The remote access aspect needs to be improved in terms of security."
"The GUI needs improvement. From a technical perspective, it's quite complex, which may not be a problem for individuals with technical backgrounds like ours, especially since we've encountered similar interfaces. However, navigating the GUI can be challenging for newcomers or product owners without technical experience. For example, as someone transitioning from a developer role to a product management role, I find it relatively easy to use the GUI. But for those without a technical background, it's much more challenging to grasp what's happening."
"Very bad support, I would rate it two out of 10."
"Support is an area where it could get better."
"Vertica seems to scale well, except for one use case where you are on a multi-node cluster. For example, if you had a nine-node cluster, one node goes down, then the eight nodes don't scale, because the absence of the node is very apparent, which is a problem. If you have nine nodes or multiple nodes, the whole idea is that if one of those nodes goes down, then you should not see an impact on the system if you have enough capacity. Even though we have enough capacity, you can still see the impact of the one node going down."
"Suboptimal projection design causes queries to not scale linearly."
"When it is about to reach the maximum storage capacity, it becomes slow."
"The integration of this solution with ODI could be improved."
"Limitations in group by projections is where I would like to see an improvement."
"The integration with AI has room for improvement."
