Versioning monitoring tables in Firebird 2.1/2.5

Firebird 2.1 added the long-awaited monitoring tables. By querying special system tables starting with MON$, you get a snapshot of the current activities in your database like who is connected to your database, which transactions and statements are running and so on. You even can cancel a running query by executing a DELETE statement on MON$STATEMENTS. Firebird 2.5 will also allow you to cancel an entire attachment via a DELETE on MON$ATTACHMENTS.

Read More on Thomas Steinmaurer’s Blog

Virtual Volumes View 0.9 released

VVV is an application that catalogs the content of removable volumes like CD and DVD disks for off-line searching.
Folders and files can also be arranged in a single, virtual file system. Each folder of this virtual file system can contain files from many disks so you can arrange your data in a simple and logical way.

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.

1 197 198 199 200 201 294