This document discusses how to prevent corruption in Firebird databases. It outlines key things to monitor like server parameters, database files, backups, and indices to recognize potential problems. Regular maintenance like validating metadata, checking backups, and analyzing logs and errors is important. The document also introduces FBDataGuard, a tool that automates monitoring of 26 database and server parameters, alerts of issues, and helps maintain databases to prevent corruption from hardware failures or other causes.
This document outlines several investment opportunities in Russian retail networks, including a stock exchange that handles over $100 million in daily turnover, a retail network called Lider with shops in 10 cities, and two building material retail networks called Baucenter with shops in 5 cities that cover over 15,000 square meters. It also mentions a shoes retail network called ECCO SHOES with a presence in 60 cities and over 100 shops.
Professional tools for Firebird optimization and maintenance from IBSurgeonAlexey Kovyazin
油
How to create better environment for big Firebird databases? How DBA can recognize and solve problems with Firebird performance, backups or corruptions (and better prevent corruptions)? This session was devoted to professional Firebird tools from IBSurgeon which help to solve all these problems.
Firebird recovery tools and techniques by IBSurgeonAlexey Kovyazin
油
Presentation "Firebird recovery tools and techniques", by Alexey Kovyazin (IBSurgeon). This presentation is devoted to Firebird corruptions: why they occur, what are their symptoms, how to fix corruptions with Firebird standard tools and with advanced IBSurgeon tools and services.
Firebird migration: from Firebird 1.5 to Firebird 2.5Alexey Kovyazin
油
This document summarizes the migration of a 75GB Firebird database from version 1.5 to 2.5 for a pharmaceutical distributor in Russia. Key steps included preparing metadata, testing the data conversion, application migration by checking and updating SQL queries, and optimizing performance. Over 55,000 SQL queries were analyzed, with around 750 requiring changes to work with the new version. The migration was completed in less than 4 months with improved performance on the new platform.
Transactions in Firebird work by assigning each record multiple versions, with each version associated with a transaction. This allows concurrent transactions to operate on stable views of the database. The transaction inventory pages (TIP) track the state of transactions and four markers - next, oldest active, oldest snapshot, oldest interesting - help determine which record versions are visible to each transaction. Keeping transactions short helps avoid problems related to these markers being out of date and prevents unnecessary record versions from building up over time.
There are more and more companies have big Firebird databases, from 100Gb till 1Tb. Maintenance and optimization tasks for such databases are different from small, and database administrators need take into account several important things about big Firebird databases.
The document discusses OLTP-EMUL, an open-source performance testing tool for Firebird. It describes how to configure and run OLTP-EMUL tests on Firebird 2.5, 3.0 and 4.0 to simulate a trading application. IBSurgeon regularly runs these tests and publishes the results online, showing significant performance improvements from Firebird 2.5 to 3.0 and 4.0, especially for the SuperServer engine. Configuration settings for Firebird.conf that optimize performance are also provided.
In this presentation we consider how to resolve Firebird performance problems: what Firebird database parameters we need to monitor and how we need to tune Firebird configuration and adjust client applications.
Firebird recovery tools and techniques by IBSurgeonAlexey Kovyazin
油
Presentation "Firebird recovery tools and techniques", by Alexey Kovyazin (IBSurgeon). This presentation is devoted to Firebird corruptions: why they occur, what are their symptoms, how to fix corruptions with Firebird standard tools and with advanced IBSurgeon tools and services.
Firebird migration: from Firebird 1.5 to Firebird 2.5Alexey Kovyazin
油
This document summarizes the migration of a 75GB Firebird database from version 1.5 to 2.5 for a pharmaceutical distributor in Russia. Key steps included preparing metadata, testing the data conversion, application migration by checking and updating SQL queries, and optimizing performance. Over 55,000 SQL queries were analyzed, with around 750 requiring changes to work with the new version. The migration was completed in less than 4 months with improved performance on the new platform.
Transactions in Firebird work by assigning each record multiple versions, with each version associated with a transaction. This allows concurrent transactions to operate on stable views of the database. The transaction inventory pages (TIP) track the state of transactions and four markers - next, oldest active, oldest snapshot, oldest interesting - help determine which record versions are visible to each transaction. Keeping transactions short helps avoid problems related to these markers being out of date and prevents unnecessary record versions from building up over time.
There are more and more companies have big Firebird databases, from 100Gb till 1Tb. Maintenance and optimization tasks for such databases are different from small, and database administrators need take into account several important things about big Firebird databases.
The document discusses OLTP-EMUL, an open-source performance testing tool for Firebird. It describes how to configure and run OLTP-EMUL tests on Firebird 2.5, 3.0 and 4.0 to simulate a trading application. IBSurgeon regularly runs these tests and publishes the results online, showing significant performance improvements from Firebird 2.5 to 3.0 and 4.0, especially for the SuperServer engine. Configuration settings for Firebird.conf that optimize performance are also provided.
In this presentation we consider how to resolve Firebird performance problems: what Firebird database parameters we need to monitor and how we need to tune Firebird configuration and adjust client applications.
Fail-Safe Cluster for FirebirdSQL and something moreAlexey Kovyazin
油
With Firebird HQbird it is possible to create high available cluster or warm standby solution. This presentation defines the problem and describes ways how to create such solutions.
FBScanner: IBSurgeon's tool to solve all types of performance problems with F...Alexey Kovyazin
油
FBScanner can be used to profile database applications, monitor user activity, manage database connections (including client disconnection on both Classic and SuperServer architecture). Its also ideal for troubleshooting INET errors (INET/inet_error: send errno = 10054), as well as auditing existing applications and performance tuning.
Understandung Firebird optimizer, by Dmitry Yemanov (in English)Alexey Kovyazin
油
The document discusses Firebird's query optimizer. It explains that the optimizer analyzes statistical information to retrieve data in the most efficient way. It can use rule-based or cost-based strategies. Rule-based uses heuristics while cost-based calculates costs based on statistics. The optimizer prepares queries, calculates costs of different plans, and chooses the most efficient plan based on selectivity, cardinality, and cost metrics. It relies on up-to-date statistics stored in the database to estimate costs and make optimization decisions.
Firebird: cost-based optimization and statistics, by Dmitry Yemanov (in English)Alexey Kovyazin
油
This document discusses cost-based optimization and statistics in Firebird. It covers:
1) Rule-based optimization uses heuristics while cost-based optimization uses statistical data to estimate the cost of different access paths and choose the most efficient.
2) Statistics like selectivity, cardinality, and histograms help estimate costs by providing information on data distribution and amounts.
3) The optimizer aggregates costs from the bottom up and chooses the access path with the lowest total cost based on the statistical information.
Firebird Scalability, by Dmitry Yemanov (in English)Alexey Kovyazin
油
In-depth presentation regarding key concepts of Firebird scalability, including SuperServer vs Classic discussion, memory usage for page and sorting buffers, CPU and concurrency, multi-CPU and multi-core, TPC-C figure, etc.
Firebird 2.1 What's New by Vladislav Khorsun (English)Alexey Kovyazin
油
Detailed presentation devoted to new features of Firebird 2.1 by Vladislav Khorsun, core Firebird Developer. Main features are covered, including tips and tricks and often usage scenarios.
仂于亠 于仂亰仄仂亢仆仂亳 Firebird 2.1 (in Russian, Vlad Khorsun)Alexey Kovyazin
油
PPT in Russian by Vlad Khorsun, core Firebird developer. Presentation is devoted to the set of new features in Firebird 2.1. Though now we have 2.5 is going to be released, it is still interesting, since many people still have 1.5 or 2.0, so 2.5 will be big move for them
Firebird Security (in English): The Past and The FutureAlexey Kovyazin
油
This document discusses the history and development of security in Firebird databases. It describes how security was initially approached for early versions of InterBase, then improvements made over time in Firebird versions 1.0 through 3.0. Key points covered include adding user authentication, addressing buffer overflows, implementing Windows trusted authentication, and plans for Firebird 3 to allow custom authentication plugins and mapping of operating system users to database roles.