May 30, 2019
Quick estimation of disk speed with backup
Is your verified backup (done with gbak) fast or no? Here are some statistics.
Is your verified backup (done with gbak) fast or no? Here are some statistics.
UDF and script to crash Firebird server
How to perform the fast conversion of Firebird database from 2.5 to 3.0
Some of you remember the article «45 Ways To Speed Up Firebird», which was published in May 2016. Now it is time to publish the next series of tips and tricks, mostly based on the experience of optimization and maintenance of the Firebird databases and servers with a high number of connections (1000+).
The excerpt from "Migration Guide To Firebird 3" is devoted to testing applications for the compatibility, after the database migration, using HQbird Standard tool: FBScanner.
More and more users upgrade to Windows Server 2016 from old versions, and some of them have noticed that Windows Server 2016 works slower than previous versions, even on the same hardware with the same database. We have made several tests and found the one option, which dramatically influences the performance of the Windows Server 2016: the power plan.
It is easy to get a powerful server if you are ready to spend many $$$. However, money is always a problem, especially for small businesses and start-ups, so there is a great demand for «good-enough» cheap solutions. This article 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 3 databases can be usually recovered from Petya's encryption with the rate close to 100%, and Firebird 2.5 database will require borrowing external metadata to save the data.
The detailed list of differences between Firebird and InterBase.
Ransomware attacks became the serious problem for many companies: during the last week we had 3 incidents from different customers which had their Firebird databases encrypted by ransomware viruses. Luckily we were able to help all of them, but the scale of the problem definitely increases. In this article, we will consider how these problems were solved.
InterBase since version 2007 supports online dump – online database file copying. Instead of gbak –b/-c this allows you to get ready to use database after copying, and you do not need to “restore” it from backup (something that is not a database). Online dump is very fast, almost like file copying by the operating system.
Firebird SQL has very suitable means to track slow SQL queries and other problems with performance through the mechanism called TraceAPI plugins. HQbird (advanced Firebird distribution for big database) includes tool FBPerfMon, which implements TraceAPI and offers easy GUI interface to track all performance problems in Firebird.
If you suspect that RAM in your server is corrupted (for example, if you see "wrong record length" errors frequently), you can use the following way to quickly check the memory with the following commands:
To enable Firebird to listen to the external requests, add to the file /etc/sysconfig/iptables the following line...
The list of all Firebird and InterBase On-Disk-Structure versions and their compatibility.
Here you can find the list of performance tips for Firebird database in different areas - from hardware/OS and Firebird tuning to SQL optimization recommendations
In order to copy users accounts (names, passwords, etc) from Firebird 2.5 security2.fdb to security3.fdb in Firebird, copy all records from RDB$USERS (security2.fdb) to PLG$USERS (security3.fdb).
Built-in functions in Firebird are faster than UDF
How to find and delete duplicate records in Firebird database
Here you can find a brief description of fb_lock_print output. Fb_lock_print provides a lot of very useful information about low-level activity of Firebird database, it is especially valuable for Classic and SuperClassic.
You can often see the following question in Firebird technical support groups: "What is the hardware of choice for the Firebird DBMS?". This topic remains permanently popular because hardware requirements differ by tasks and hardware itself changes with time.
Firebird Project has released Firebird 2.5.5. his minor release has many bug fixes and highly recommended to be used in production environments, especially if you are running Firebird 2.5.0, 2.5.1, 2.5.3 or 2.5.4 – upgrade to 2.5.5 as soon as possible!
This article was initially intended for Firebird DBMS developers and administrators, but contacts with administrators of other databases made it clear that most mistakes are common among them as well and literally everyone stumbles over nearly the same stones. If you can add something to this list (even something specific to a particular DBMS), contact us via our e-mail or post it in the comments
Official Firebird 3.0 Release Candidate is available for testing - download Windows and Linux versions
As you may know, in 2005-2006 our company was the publisher of «The InterBase and Firebird Developer Magazine». Here you can read all 4 issues of this magazine.
Update of our popular presentation about fixing Firebird problems.
Here you can find a copy of Release Notes for Firebird 3 RC1
Firebird 3 Quick Start Guide - Initializing security database. Initialization is performed in embedded mode using the isql utility. For an embedded connection, an authentication password is not required and will be ignored if you provide one. An embedded connection will work fine with no login credentials and “log you in” using your host credentials if you omit a user name.
This presentation is the very short version of our course "How Firebird transactions work"
In general, indices are necessary for any serious database, since they are critical to speed up queries with WHERE clause (SELECT, UPDATE. MERGE, DELETE, etc). However, every index has the cost, and the cost is obvious when we compare the speed INSERT/UPDATE/DELETE operations on indexed and non-indexed fields.
Presentations, materials and photos from Firebird Conference 2014 (Prague, Czech Republic, October 24-25, 2014).
This article briefly describes the serious errors (bugchecks) in Firebird and InterBase.
An explanation of command line parameters for Firebird 3 installer.
How to use installer of Firebird 3.0 to install and uninstall it.
List of known incompatibilities between versions 2.x and 30 (not completed)
This article is devoted to the tuning of 1.7Tb FirebirdSQL database.
Some days ago we have published an article about our tests, devoted to the relationship between Firebird performance and databases growth, where we have tested 1.7 terabyte Firebird SQL database. Here you can find more details about such a big database.
As you may noticed, our web-site www.ib-aid.com (www.ibsurgeon.com) has got a new look recently. This new web-site is running CMS FireWeb which uses Firebird 2.5.2 as a backend, so we decided to tell you more about its capabilities.
Recently in IBSurgeon we made series of performance tests with Firebird 2.5.2. Firebird 2.5.2 is the most popular version of Firebird database, and its users often have questions, related with Firebird performance.
When gfix.exe finishes it writes a summary of errors (if any) to the standard output (normally to the screen). Here is a short explanation of gfix output.
Here you can find a detailed overview of most popular Firebird/InterBase corruption reasons.
1 Tb Firebird database: preliminary report about test 1 terabyte Firebird database
Description of common errors and problems in InterBase/Firebird databases and their recovery chances.
IBAnalyst: How to get statistics from InterBase/Firebird database in right way
IBAnalyst: what you can see at Summary View
An article from "The InterBase and Firebird Developer Magazine" about IBAnalyst
A questionnaire for those who have performance problems with Firebird databases. These questions cover most popular performance problems with Firebird or InterBase databases.
Internal gds software consistency check - here is the full list of serious Firebird/InterBase errors
After fixing corruptions it's a often to see "Cannot commit index" error at restore step. Here is a short guide how to workaround this issue.