Ingres began as a research project at the University of California, Berkeley, starting in the early 1970s and ending in 1985. The original code, like that from other projects at Berkeley, was available at minimal cost under a version of the BSD license. Ingres spawned a number of commercial database applications, including Sybase, Microsoft SQL Server, NonStop SQL and a number of others. Postgres (Post Ingres), a project which started in the mid-1980s, later evolved into PostgreSQL. It is ACID compatible and is fully transactional (including all DDL statements) and is part of the Lisog open-source stack initiative.
We support Ingres directly in our products! You don't need separate drivers and can immediately connect to your database.
All our products support Ingres database natively. No drivers are needed, you will be able to work with Ingres as soon as you run our applications.
It may make sense to migrate your data away from Ingres. You may want to do it permanently or just need to share your tables with a collague in a different format.
We will copy all your tables with their data and apply indexing and relationships exactly as they are in your current Ingres database. In a nutshell, you get exactly the same database in another database engine. Each time you run the migration, we will copy all the tables again. Of course, we have a built-in scheduler, so you can run this overnight and have a fresh database copy in the morning.
Have a need to import data from various sources into your Ingres database? Luckily we support many popular database formats to make this easy for you. Instead of messing with exporting from source, then working your way to somehow import data into Ingres, use our tool to copy all desired tables directly - quickly and easily.
If you have already created your target database (by yourself or using our Full Convert, Exporter or Importer products), you can synchronize data in your target database with your original Ingres database. We never pollute your databases with additional tables or triggers for replications. We never even write to your source database.
Replication allows you to update your target database very often, as we always write just a minimum of changes needed to bring databases in sync. For example, if you added three records to a single table in your Ingres database, our replication product will write those three records to target database and nothing else. If you deleted some records, changed some others and inserted some, again – our product will pick that up and replay those changes in the target databases without touching existing data that should stay there. Our products are highly optimized for real-world workloads, so data that's inserted into different areas of table are combined and written using high-speed algorithms, as available in a specific target database.
You can run database replication often, as your target database is never empty while replication runs. You will simply see that your changes are applied on each run.
When you want a stellar SQL writing experience, our Query allows you to easily and quickly write your queries. It will autocomplete as you type and allow you to instantly view your data.
Database diagrams only get you so far. You may want to keep HTML mini-website for your database documentation so all your developers can be in the loop and quickly locate needed information. You may need it for a client report, or to distribute your database schema as a CHM file to people who need it.
Our products even allow you to upload the documentation to your FTP server, so your website copy is always current.