Recommended update – Firebird 2.1.1

The recent release of Firebird version 2.1.1 is very welcome.

Here are a few of the fixes I consider important for 2.1 production servers and so recommend the update:

  • Stability fixes for the monitoring tables
  • Fixed possible corruption of the users database, security2.fdb.
  • Fixed nBackup, which did not work in version 2.1.
  • Fixed a memory leak on DDL statements.

The complete list of bugs fixed and the downloads are at the Firebird SQL website.

Firebird SuperClassic – Another option

Called SuperClassic, it will be the basis for the multi-processor support that we’ll see in Firebird 3.0.

Don’t lose count. Starting from Firebird 2.5 you will be able to choose among SuperServer, ClassicServer and SuperClassic.

Basically SuperClassic is like ClassicServer. Only instead of a process for each attachment it uses a single process with a thread for each attachment. The benefit being that it uses fewer kernel resources and is a bit faster.

Read a deeper comparison between the three architectures.

Red Database 2.1 released – merge ideas

Hello, Dear Firebird Team Members!

After almost two years in development, four betas and four release
candidates, Red Database 2.1 is finally released.

Information about the release is present here:
http://www.red-soft.biz/en/index.html

Apache, PHP and Firebird Performance Tuning

In the last post I commented that I had a test-bed application, based on ApachePHP and Firebird, and once the problem with the images was solved I could finally start doing the actual performance testing/tuning that I originally wanted to do. 

The only major changes from the last post is that I’ve now upgraded the database engine to the “Firebird v2.5 Alpha 1” that supports SMP, and that the application now contains more base data in the tables.

Progress on the Entity Framework Provider for Firebird

Today, after some days/weeks, I finally created some noticable (= not only internals) progress with Entity Framework provider for Firebird.

Now, the provider is able to use, map, call, … stored procedures (and functions [very experimental]). You can select stored procedures from database, map these to some operations in EF, create “function imports” etc. You can see this working on picture:

1 200 201 202 203 204 296