Azure Synapse Analytics vs. OpenText Vertica

In terms of a well-suited scenario - the Azure Synapse can be used to capture data from multiple sources (especially from onPrem sources apart from Dataverse) and update the transformed data based on the given conditions (eg: refresh data based on the specified date/time ranges). Also, the transformed data can simply be transferred to Azure Data Lake for further processing by utilizing other analytics tools such as PowerBI.

Incentivized

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.

Incentivized

• The combination of SQL/unstructured data
• Keeping things "complicated, but simple"; [heterogeneous] data formats seen as just SQL tables to business experts used to use Power BI, Excel, and any other traditional SQL-oriented BI tools
• Integration options using "Synapse pipelines", the application of ADFs
• The greatly integrated solution of independent things (Spark MPP cluster, MPP SQL Servers, ADFs) - all sitting under one roof. Great job!
• Integration with super-fast, globally replicated data. I really appreciate the integration of NoSQL databases (namely Core API and Mongo API under Cosmos DB) with purely batch-processed BI data

Incentivized

• 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.

Incentivized

• With Azure, it's always the same issue, too many moving parts doing similar things with no specialisation. ADF, Fabric Data Factory and Synapse pipeline serve the same purpose. Same goes for Fabric Warehouse and Synapse SQL pools.
• Could do better with serverless workloads considering the competition from databricks and its own fabric warehouse
• Synapse pipelines is a replica of Azure Data Factory with no tight integration with Synapse and to a surprise, with missing features from ADF. Integration of warehouse can be improved with in environment ETl tools

Incentivized

• 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.

Incentivized

The data warehouse portion is very much like old style on-prem SQL server, so most SQL skills one has mastered carry over easily. Azure Data Factory has an easy drag and drop system which allows quick building of pipelines with minimal coding. The Spark portion is the only really complex portion, but if there's an in-house python expert, then the Spark portion is also quiet useable.

Incentivized

Microsoft does its best to support Synapse. More and more articles are being added to the documentation, providing more useful information on best utilizing its features. The examples provided work well for basic knowledge, but more complex examples should be added to further assist in discovering the vast abilities that the system has.

Incentivized

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.

Incentivized

They're all part of the Microsoft Azure family, so they are not exactly competitors. They overlap in functionality, but they're targeted at different levels of customers. Azure Data Factory is an excellent stand-alone PaaS (included in Synapse Analytics) for writing, scheduling, and monitoring pipelines. Azure SQL Database (and all the Azure SQL family) is excellent for traditional, SQL-based data warehouses, especially if you're migrating from on-premises. Combined with Azure Data Factory (that can run SSIS packages), it's a perfect solution for a simple path to the cloud. Azure Databricks is effectively the only internal "competitor" to Synapse Analytics but targeted more to a "platform-agnostic" audience. On the other hand, Synapse is more of a proprietary mix of products that are more tightly related to Microsoft technologies.

Incentivized

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.

Incentivized

• It definitely has a positive impact on ROI. We are able to use it to generate MORE revenue through predictive analytics and pricing optimization.
• Because of the SQL Data Warehouse design, we're able to set up some self service reporting tools which allow our users to generate reports ad hoc instead of having a full time employee creating these by hand.
• Having visibility into the data is very useful for management to make good business decisions.

Incentivized

• Vertica increased our productivity in analyzing the data and validating simple proof of concepts with our data.
• Results of analytical queries produced from Vertica are used by all departments as well as part of some of our products.

Incentivized