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“.
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+).
If you installed Firebird ADO.NET provider 184.108.40.206 and EntityFramework.Firebird from nuget you also need to add the DDEX provider for Firebird into Visual Studio 2017 following these steps.