embedded-database

Has anybody done any benchmarking/evaluation of the popular open-source embedded SQL DBs for performance, particularly write performance? I've some 1:1 comparisons for sqlite, Firebird Embedded, Derby and HSQLDB (others I am missing?) but no across the board comparisons... Also, I'd be interested in the overall developer experience for any of these (for a Java app). This benchmark from db4o might be helpful. It includes, JavaDB (Built on top of Derby), HSQLDB, SqlLite. It seems HSQLDB out-performs its counterparts, especially when writing is concerned. H2, as a successor of HSQLDB, is faster

I'm currently using the following setup to create a schema in an embedded database before running my tests against it In my application context <jdbc:embedded-database id="dataSource" type="HSQL"> <jdbc:script location="classpath:createSchema.sql" /> </jdbc:embedded-database> createSchema.sql create schema ST_TEST AUTHORIZATION DBA; hibernate properties <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect" /> <property name="hibernate.default_schema" value="ST_TEST"/> <property name="hibernate.hbm2ddl.auto" value="create-drop" /> <property name="hibernate

I will be building a set of applications. One of these apps is unattended application (written in VB6) which will write data it receives from various sources to a local database. All the other applications (will be written in VS 2008/c# 3.0) will read this data for mostly reporting reasons. I don't want SQL Server/MySql/Sybase or even its express editions, because distributing it is a problem (e.g. requires separate install, etc...). I am looking for a local database that has drivers for both VB6 (so probably OLEDB, or ODBC if I have to settle for it) and ADO.NET. It would also be nice, if the

I am looking for satisfactory options for unit testing my .NET DAL classes; since they're DAL classes, they access the database directly using ADO.NET. Presently I use an instance of a MSSQL database for the testing, but was wondering what faster options there are---since unit tests need to run as quickly as possible, an in-memory solution would be ideal. I should also mention that I have tied myself to TSQL since I'm only ever going to be using a Microsoft platform. Given that you state: I should also mention that I have tied myself to TSQL since I'm only ever going to be using a Microsoft

I am collecting data and store this data in a MySQL database using Java. Additionally, I use Maven for building the project, TestNG as a test framework, and Spring-Jdbc for accessing the database. I've implemented a DAO layer that encapsulates the access to the database. Besides adding data using the DAO classes I want to execute some queries which aggregate the data and store the results in some other tables (like materialized views). Now, I would like to write some testcases which check whether the DAO classes are working as they should. Therefore, I thought of using an in-memory database

I need to build a simple, single user database application for Windows. Main requirements are independence from windows version and installed software. What technologies (language/framework) would you recommend? My preference for language is the Visual Basic. EDIT: What about VB.Net and SQL Server Compact Edition? I would recommend Sqlite . It's completely self-contained, and public domain so there are no license issues at all. Single user or multi user? For single user, the answer would be SQLite For multi user (or multithread), try MySQL or PostgreSQL . Since your requirement is a windows