Firebird

Firebird . Open source relational database management system boasts excellent performance and scales impressively, from an integrated, single-user model, to multi-database business developments of more than 500 Gb, with hundreds of concurrent clients . Firebird is an open source relational database management system (or RDBMS) (Query Language: SQL ), based on version 6 of Interbase, the code of which was released by Borland in 2000. Its code was rewritten from C to C ++. . The project is actively developing, on April 18 , 2008 version 2.1 was released and theAs December 26 as 2009 it was released 2.5.0 RC1 version.

Summary

[ hide ]

  • 1 FirebirdSQL
  • 2 History
  • 3 Versions
  • 4 Features
  • 5 Types of Server
  • 6 External links
  • 7 Source

FirebirdSQL

It is the foundation that maintains and develops Firebird, it is fundamentally based on supporting and achieving the advancement of the Firebird relational database manager, providing non-commercial mechanisms and infrastructure to accept and manage the funds raised, and investing such funds to promote the effort the development of this database, encourage the cooperation and affiliation of individuals, non-profit organizations, and commercial companies involved or planning to be involved in the development, support, and promotion of Firebird software projects and products, and associated activities.

History

In the late 1990s , Borland decided to release the code from Interbase. Various staff members created a new company called IBPhoenix , and together with other independent developers, created the Fork now known as Firebird. Borland would later decide to re-privatize Interbase and market its licenses. However, Firebird is still an open source project under a license similar to the MPL (Mozilla Public License).

Firebird technology has been in use for 20 years, making it a very stable and mature product.

Versions

The development of Firebird brings with it the appearance of versions that include new features and possibilities. This is how it started with version 1.0 (simply porting the internal 6.0 code in C ), version 1.5 (conversion of firebird to C ++ ), version 2.0 (new features such as derived tables, etc.), version 2.1 (management features sessions, etc) and so on until the last scheduled, version 3.0. These themes are written with the features up to the current version available (2.5) so some features may not be available in previous versions.

characteristics

  • Full support for Stored Procedures and Triggers.
  • 100% ACID transactions.
  • Referential integrity.
  • Multi-generational architecture.
  • Low consumption of resources.
  • Complete internal language for stored procedures and triggers (PSQL).
  • Support for External Functions (UDFs).
  • Little or no need for specialized DBAs.
  • Virtually no configuration required – just install and start using.
  • Great community and many sites where you can find excellent free support.
  • Embedded Version – Ideal for creating CD-ROMcatalogs , single user, evaluation, or portable versions of applications.
  • Dozens of third-party tools, such as graphical management tools, replication tools, etc.
  • Secure writing – fast recovery, without requiring transaction logs.
  • Many ways to access the database: native / API, dbExpress, ODBCOLEDB drivers, .Net provider, native type 4 JDBC driver, Python, PHP, Perl module, etc.
  • Native support for all major operating systems, including WindowsLinux , Solaris , Mac OS .
  • Incremental backups.
  • Availability of binaries in 64-bit architecture.
  • Full implementation of cursors in PSQL.
  • Monitoring Tables.
  • Connection and Transaction level triggers.
  • Temporary Tables.

Server Types

There are two types of Firebird servers to be installed: Classic and Super server. Although they have several minor differences between them, the main one is that the super server handles individual threads of execution for each connection. Therefore, for a reduced number of connections, the recommended would be the classic because it will consume less resources.

In the case of SMP architectures, the classic server must be used because the Supersever does not have support for this type of architecture.

The Firebird developers themselves recommend the following when deciding on one of these servers:

  • On Windows platforms select the Superserver.
  • In Linux simply choose any one, based on the estimated connections. In most situations there will be no difference in performance.

It could be considered a third type, the Embedded. This consists of a single DLL dynamic link library (about 2 MB in size) that contains the entire server. In this way you can have a complete DBMS available and distributable together with user applications without requiring that it be installed separately.

 

Leave a Comment