Developer News Archives - Page 8 of 57

Fast, Furious, and Cheap: server with good-enough performance for small business database for less than US$1000

It is easy to get a powerful server if you are ready to spend many $$$: there are leading vendors like Dell, HP, and many less known hardware companies, they will be happy to sell you a powerful machine.
However, money is always a problem, especially for small businesses and start-ups, so there is a great demand for «good-enough» cheap solutions.

The new article from IBSurgeon describes the practical approach for building «good-enough» database server with the sufficient performance for small business. It also contains calculations and links to the specific products we recommend.

Firebird 4 alpha

Firebird Project announces the first Alpha release of Firebird 4.0, the next major version of the Firebird relational database, which is now available for testing.

This Alpha release arrives with an early preview of the features and improvements currently under development by the Firebird development team, as well as with countless bugfixes. Our users are appreciated giving it a try and providing feedback to this mailing list. Apparent bugs can be reported directly to the bugtracker.

Alpha releases are not encouraged for production usage or any other goals that require a stable system. They are, however, recommended for those users who want to help in identifying issues and bottlenecks thus allowing to progress faster through the Beta/RC stages towards the final release.

Please read the Release Notes carefully before installing and testing this Alpha release.

Download page:
http://www.firebirdsql.org/en/firebird-4-0-0-alpha1/

Release Notes:
http://web.firebirdsql.org/downloads/prerelease/v40alpha1/Firebird-4.0.0_Alpha1-ReleaseNotes.pdf

—
Dmitry Yemanov

Fighting Petya: our experience with retrieving data from the Firebird database files encrypted by ransomware crypto-viruses

As you know, recently several crypto viruses have attacked many companies – most well-known are Wannacry and Petya. Usually, as reported by many companies, it is necessary to pay a ransom, or, in the case of Petya, all encrypted files will be lost.

Read how we can defeat Petya:
https://ib-aid.com/en/articles/fighting-petya-our-experience-with-retrieving-data-from-the-firebird-database-files-encrypted-by-ransomware-crypto-viruses/

HQbird 2017R2

HQbird 2017R2 is a major upgrade of advanced Firebird distributive (versions 2.5 and 3.0) with high-availability, replication, optimization, monitoring and recovery tools. Please upgrade the previous version of HQbird with 2017R2 (this upgrade is free for all users of HQbird).

This release includes a lot of improvements in replication, monitoring, and optimization, as well as many bugfixes. Windows installer now supports an automatic upgrade of the existing HQbird installation, Linux support for auto-upgrade will be released later.

The main goal of HQbird 2017R2 is to provide administrators and developers of big Firebird databases with effective management, maintenance, recovery, and optimization tools, in order to keep databases always healthy and available.

More details about HQbird: https://ib-aid.com/hqbird

Jaybird 3.0.1 released

The Firebird JDBC team is happy to announce the release of Jaybird 3.0.1.

Jaybird 3.0.1 contains the following fixes and changes:

Fixed: FBTraceManager.loadConfigurationFromFile strips line breaks (JDBC-493)
Fixed: FBDatabaseMetaData.getTables does not list tables where rdb$relation_type is null (JDBC-494)
Improvement: Character sets are now initialized lazily (JDBC-495)
Fixed: Memory leak caused by retaining blob handles until connection close (JDBC-497)

See the Jaybird 3.0.1 release notes for more information. Jaybird 3.0.1 can be downloaded from the JDBC Driver page.

JayBird 3 is released

We are happy to announce the release of Jaybird 3.0.0.

Jaybird 3.0 is a big change from Jaybird 2.2 and earlier. The entire low-level implementation has been rewritten to be able to support protocol improvements in newer Firebird versions. We have also made changes with a stricter interpretation of the JDBC requirements, and removed some parts that were either obsolete or not functioning correctly.

Most notable changes in Jaybird 3:

Support for wire protocol versions 11, 12, and 13 (without support for encryption and compression); protocol version 13 contributed by Hajime Nakagami
Support for the Firebird 3 SRP (Secure Remote Password) authentication mechanism (contributed by Hajime Nakagami)
Support for streaming backup and restore (contributed by Ivan Arabadzhiev)
Improved Firebird 3 support
Improved and stricter JDBC support (including improved java.time support, and more optional methods implemented)
Initial JDBC 4.3 (Java 9) support (without real module support)
New implementation of the native/embedded Type 2 driver using JNA (a jaybird .dll/.so is no longer needed)
Improved character set handling
Removal of (buggy) connection pool implementation
Removal/replacement of (internal) GDS API

And a large number of smaller bug fixes, improvements, and changes.

We recommend that you do not consider Jaybird 3.0 a drop-in replacement for Jaybird 2.2, and study the release notes carefully. Test your application with Jaybird 3.0 before using it in production.

Jaybird 3.0 supports Firebird 2.0 and higher, on Java 7, 8 and 9. Basic Java 9 compatibility is provided through the Java 8 version of the driver.