Apache Derby is a DB subproject of Apache Software Foundation. It’s one of its commercial-quality, open-source database solutions licensed for distribution at no charge to the public.
Derby roots are in JDBMS database developed by Cloudscape back in 1997. Renamed to Cloudscape, then acquired by Informix, which was in turn acquired by IBM in 2001. IBM, contributed the database code to Apache in 2004.
Derby is based on Java, SQL and JDBC standards. It includes embedded JDBC driver, so it can be included in any Java-based application. Derby is extremely small – complete database engine and its embedded driver consume just 2.6MB of space. It can even be used in a client/server mode, not only as an embedded solution.
It’s very easy for Java applications to use Derby as its data store. However, it’s not really a good client/server solution. With rather low performance and locking issues, you may want to reconsider your database choice unless all you need is an embedded database (also, a well-known embedded alternative is SQLite). Users report Derby to be a rock-solid embedded database. Keep in mind its modest performance. Complex queries have significant hit on Derby performance, as well. In H2 database’s comparison of H2, HSQLDB and Derby, Derby turned out to be the slowest of the Java embedded databases.
Sun Corporation packaged Derby as JavaDB in JDK 6 and today Oracle (who acquired Sun) continues that practice. IBM packages Derby as Cloudscape.
All our applications are .NET applications. We opted to support Java-based Derby by migrating it to .NET platform using IKVM.NET, which automatically migrates Java bytecode to .NET bytecode. Therefore, we have native support for Derby and can read, write and query Derby.
All our products support Derby database natively. No drivers are needed, you will be able to work with Derby as soon as you run our applications.
It may make sense to migrate your data away from Derby. 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 Derby 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 Derby 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 Derby, 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 product), you can synchronize data in your target database with your original Derby 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 Derby 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.