We performed a comparison between Actian Ingres and Snowflake based on real PeerSpot user reviews.
Find out what your peers are saying about Snowflake Computing, Oracle, Teradata and others in Data Warehouse."The deployment of our solution across a number of servers using Ingres .NET has meant that we can protect the database server behind a highly secure firewall and deploy the front end solutions on a normal web server."
"The features that I have found most valuable are the ease of use, the rapidness, how quickly the solution can be implemented, and of course that it's been very easy to move from the on-premise world to the Cloud world because Snowflake is based on SQL also."
"The product's most important feature is unloading data to S3."
"Once you have finished your designs they can be easily imported to Snowflake and the information can be readily accessed without an IT expert."
"It requires no maintenance on our part. They handle all that. The speed is phenomenal. The pricing isn't really anything more than what you would be paying for a SQL server license or another tool to execute the same thing. We have zero maintenance on our side to do anything and the speed at which it performs queries and loads the data is amazing. It handles unstructured data extremely well, too. So, if the data is in a JSON array or an XML, it handles that super well."
"The snapshot feature is good, the rollback feature is good and the interface is user-friendly."
"The solution is very easy to use."
"The ability to share the data and the ability to scale up and down easily are the most valuable features. The concept of data sharing and data plumbing made it very easy to provide and share data. The ability to refresh your Dev or QA just by doing a clone is also valuable. It has the dynamic scale up and scale down feature. Development and deployment are much easier as compared to other platforms where you have to go through a lot of stuff. With a tool like DBT, you can do modeling and transformation within a single tool and deploy to Snowflake. It provides continuous deployment and continuous integration abilities. There is a separation of storage and compute, so you only get charged for your usage. You only pay for what you use. When we share the data downstream with business partners, we can specifically create compute for them, and we can charge back the business."
"The pricing is reasonable and matches the rest of the market."
"The ability to reset the log file without stopping the DBMS would be helpful for us."
"It doesn't enforce typical relational database constraints. Quite expensive."
"We would like to be able to do modeling with Snowflake. It should support statistical modeling."
"The aspect of it that was more complicated was stored procedures. It does not support SQL language-based stored procedures. You have to write in JavaScript. If they supported SQL language and stored procedures, it would make migration from on-prem much simpler. In most cases, if an on-prem solution has stored procedures, they're usually written in SQL. They're not written as what most on-prem DBMS would refer to as an external stored procedure, which is what these feel like to most people because they're written in a language outside of SQL."
"Portability is a big hurdle right now for our clients. Porting all of your existing SQL ecosystem, such as stored procedures, to Snowflake is a major pain point. Currently, Snowflake stored procedures use JavaScript, but they should support SQL-based stored procedures. It would be a huge advantage if you can write your stored procedures using SQL. It seems that they are working on this feature, and they are yet to release it. I remember seeing some notes saying that they were going to do that in the future, but the sooner this feature comes out, it would be better for Snowflake because there are a lot of clients with whom I'm interacting, and their main hurdle is to take their existing Oracle or SQL Server stored procedures and move them into Snowflake. For this, you need to learn JavaScript and how it works, which is not easy and becomes a little tricky. If it supports SQL-based procedures, then you can just cut-paste the SQL code, run it, and easily fix small issues."
"Product activation queries can't be changed while executing."
"Snowflake could improve if they had an Operational Data Store(ODS) space."
"They need to improve its ETL functionality so that Snowflake becomes an ETL product. Snowpipe can do some pipelines and data ingestion, but as compare to Talend, these functionalities are limited. The ETL feature is not good enough. Therefore, Snowflake can only be used as a database. You can't use it as an ETL tool, which is a limitation. We have spoken to the vendor, and they said they are working on it, but I'm not sure when they will bring it to production."
"There are three things that came to my notice. I am not very sure whether they have already done it. The first one is very specific to the virtual data warehouse. Snowflake might want to offer industry-specific models for the data warehouse. Snowflake is a very strong product with credit. For a typical retail industry, such as the pharma industry, if it can get into the functional space as well, it will be a big shot in their arm. The second thing is related to the migration from other data warehouses to Snowflake. They can make the migration a little bit more seamless and easy. It should be compatible, well-structured, and well-governed. Many enterprises have huge impetus and urgency to move to Snowflake from their existing data warehouse, so, naturally, this is an area that is critical. The third thing is related to the capability of dealing with relational and dimensional structures. It is not that friendly with relational structures. Snowflake is more friendly with the dimensional structure or the data masks, which is characteristic of a Kimball model. It is very difficult to be savvy and friendly with both structures because these structures are different and address different kinds of needs. One is manipulation-heavy, and the other one is read-heavy or analysis-heavy. One is for heavy or frequent changes and amendments, and the other one is for frequent reads. One is flat, and the other one is distributed. There are fundamental differences between these two structures. If I were to consider Snowflake as a silver bullet, it should be equally savvy on both ends, which I don't think is the case. Maybe the product has grown and scaled up from where it was."
Earn 20 points
Actian Ingres is ranked 22nd in Data Warehouse while Snowflake is ranked 1st in Data Warehouse with 94 reviews. Actian Ingres is rated 9.0, while Snowflake is rated 8.4. The top reviewer of Actian Ingres writes "Good multi-platform SQL compatibility, as well as performance and data integrity". On the other hand, the top reviewer of Snowflake writes "Good usability, good data sharing and elastic compute features, and requires less DBA involvement". Actian Ingres is most compared with Oracle Database Appliance, Databricks and Teradata, whereas Snowflake is most compared with BigQuery, Azure Data Factory, Teradata, Vertica and AWS Lake Formation.
See our list of best Data Warehouse vendors and best Cloud 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.