Actian Ingres Reviews

We run the entire IRS system, the income system, and the tax system. We also manage the entire Absa banking system in Africa. There's a lot of database applications, similar to those used in banks and the IRS.

The most valuable features for us are reliability and performance. Our system is used for the Lufthansa flight scheduling system and the real-time plane diverting system. The systems need to be robust enough to stay up to date. It's about having robust, trustworthy solutions that people can rely on.

The seamless integration is a bit of an issue. I would like to see more direct connectors and stuff like SQLAlchemy. It's there but isn't available as a standard, so it involves going to GitHub to access it.

We have used this solution for more than ten years.

The solution is very stable. We haven't heard of any issues, even from significant users like the London Stock Exchange.

We have load-sharing capability, and we have upgraded the system to be more analytical by integrating VectorWise into the Ingres Database. The deployment can scale horizontally easily.

Pretty good. We won a few awards for it. It's the typical follow-the-sun support, providing 24/7 worldwide assistance.

Positive

I used Netezza in the past, however, I joined another company over a year ago.

The setup is pretty straightforward. It's very reliable and fast, and works well with typical OLTP setups.

Companies like Lufthansa and the Irish Revenue would not have stayed with us for many years if there wasn’t a return on investment.

Initially, it's a lot less expensive than competitors. Price performance has always been a priority, ensuring we remain competitive in the market.

Overall, I would rate Ingres a seven or eight out of ten. In terms of competitiveness, it's pretty good. It's critical to our operations, especially with analytical enhancements.

We currently run Web server solutions (CMS, CRM business solutions).

Our CMS solution is obviously very text-oriented, and our CRM Business Solution was built for a finance and asset management business, which is capable of handling millions of transactions.

Performance, access control, data integrity are fundamental to any application but we have been able to more than satisfy our clients with the solutions we have delivered.

We have Ingres running on an AWS Linux server. We have Windows Server running front end solutions using Ingres OpenRoad and Linux Servers serving Web Applications through Apache and PHP.

Ingres is the only database solution that has maintained a level of consistency and integrity about the way users interact with it. As a database administrator, there is a level of transparency and control at all levels.

Over the last few years, we have migrated all of our business functional logic into database procedures, which improves performance significantly and allows us to alter our development tools/programming languages easily.

Our products CK5 and JS5 are offered as SaaS solutions through jetpac.co.nz

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 User is never exposed to any configurations or logins other than their own initial identification.

The SQL capability is consistent across all platforms. This means that we can code into our PHP functions to manage the database so that the users can be generally self-sufficient and requiring DB support only rarely.

Whilst our server up-time is in the > 99%, we still have to reboot the DBMS periodically to allow us to archive the log file. The ability to reset the log file without stopping the DBMS would be helpful for us.

We have created our own error management/reporting process within our database procedures. Unfortunately, if there is a database error, such as a duplicate key, the default action is to abort. This means that our information is generally lost. An option to not abort on failure would be great. Of course, this only really occurs in testing.

I first came across Actian Ingres in 1992 and have been using it in all of my solutions since then.

It is completely scalable, as the Query Execution Process is completely dynamic based on the current number of rows and efficiency of the index structures.

We did not use another solution, as this was a greenfield opportunity

We evaluated Oracle and DB2.