More info at this link.
As you probably know, Firebird Conference 2019 will include the practical workshops, and the article “How to track deadlocks in Firebird” is one of the sneaks peeks of the workshop “All About Transactions”, which will be done by Vlad Khorsun, Firebird core developer, and Alexey Kovyazin from IBSurgeon.
To help developers investigate the update conflicts (deadlocks), Firebird puts into error messages the reference to the concurrent transaction – i.e., the transaction where the concurrent update is not yet committed. Together with Trace API, it gives us the ability to track both conflicting operations.
Let’s consider the practical steps on how to do it: read the article “How to track deadlocks in Firebird“.
We are pleased to announce a significant extension of the Firebird project to a whole new area. Starting in February 2019, alongside the core (Firebird database system) and database drivers, a completely new division called Firebird Butler is integrated into the project. The purpose of the Butler division is to develop and provide solutions to various Firebird-related challenges faced by Firebird administrators and application developers that, for practical reasons, are not addressed by the core Firebird distribution.
The primary aim of Firebird Butler is to create a development platform and develop a set of basic solutions to manage Firebird installations of any size, structure and complexity. The emphasis is on large corporate installations but the scope and ambitions of the Firebird Butler project are much broader: we would like to initiate development of an entire open source ecosystem of projects and other products, including commercial ones, in various languages. Projects could encompass not just the planned new services, but alternative implementations of the standard services as well. Moreover, the Firebird Butler Development Platform should become a solid foundation for development of any applications that use Service Oriented Architecture and messaging.
For a closer look at the project goals and strategies, please read the “Introduction to Firebird Butler”.
Although the project is only in the early stages of development, we encourage you to take a close look at what we have and where we are going. The project is completely open, and we will welcome anyone, individuals or organizations, who is interested in the objectives and strategy of the project and wishes to participate in its development, in a common or entirely private capacity, or to become its sponsor.
Firebird Butler also presents a great opportunity for developers with experience in Python, Java, FreePascal, Delphi, C# or other languages to get involved in Firebird project activities.
The Firebird Project Team
FbNetExternalEngine is plugin for Firebird 3+ that allows you to write stored procedures, functions (not yet) and triggers (not yet) in any .NET language. There’s no limitation on what you can or cannot do in the code. Full power of .NET and .NET eco-system is available for you.
More info here.
The new article with the collection of tips and tricks to improve Firebird database performance: 23 More Ways To Speed Up Firebird. The article is based on the appropriate presentation from “Firebird Performance Tour” seminar.
Why “23 more”?
Some of you can remember the article 45 Ways To Speed Up Firebird, which was published in May 2016. Now it is time for some more tips and tricks, mostly based on the experience of optimization and maintenance of the Firebird databases and servers with the high number of connections (1000+).