The various system tables — RDB$ and MON$ — and associated indices are created, and appropriate pages formatted and written to disc; • Every page in the database is formatted with a defined page type database file, or files, with enough space allocated to create all the system tables and indices. New pages will be added to the end of the database file(s) as and when the user creates new tables and/or indices total of 0xa1 pages (161 pages) for the system tables, indices and the various database overhead pages. 2.1. Single File Databases A single file Firebird database consists of a number of pages, each the

Contents 1 Chapter 1. Introduction Firebird uses a page cache to hold pages in memory. It is much quicker to retrieve pages from RAM than to go out onto the disc system and read them physically each up from hibernation and the cause was thought to be the time required to load back all the cache pages from disc before the first query (after hibernation) could be processed. The cause was confirmed Firebird Cache Everything in the database is organised as fixed sized pages of known structure - there are nine different types of pages. The page cache is the intermediate between the "working" parts of

Set Database Page Buffers The database cache is an area of RAM allocated to store (cache) database pages in memory to help improve the efficiency of the database performance. It is far quicker to read data database gets its own relatively small cache of 256 pages (was 75 before Firebird 3.0) while Superserver creates a much larger cache of 2048 pages which is shared between all the connections. Usually careful). The command to set the number of cache pages is: gfix -b[uffers] BUFFERS database_name This command allows you to change the number of buffers (pages) allocated in RAM to create the database cache

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 RDB$PAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fit onto one data page, its contents are put onto separate pages allocated exclusively to it (blob pages), while the numbers of these pages are stored into the BLOB record. This is a level 1 BLOB. • the BLOB data does not fit onto a data page, the array is put on separate blob pages, while the numbers of these pages are put into the BLOB record. This is a level 2 BLOB. • Levels higher than 2 are

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 RDB$PAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fit onto one data page, its contents are put onto separate pages allocated exclusively to it (blob pages), while the numbers of these pages are stored into the BLOB record. This is a level 1 BLOB. • the BLOB data does not fit onto a data page, the array is put on separate blob pages, while the numbers of these pages are put into the BLOB record. This is a level 2 BLOB. • Levels higher than 2 are

-BU[FFERS] This switch sets the default database cache size (in number of database pages) for the database being restored. If a database is being overwritten then this setting will overwrite specified, all database pages will be filled to 100% and no free space will be left for updates. Use of this switch set a flag in the database header page to signal that all pages are to be filled to 100% 100% — this applies to any new pages created after the restore. You can override this setting, using gfix -use full | reserve database_name Chapter 2. Command-line Options 11 where full uses 100% of

....................................................................................... 671 RDB$PAGES ................................................................................................. 'baseserver:D:\test.fdb' USER wizard PASSWORD 'player' ROLE 'RDB$ADMIN' PAGE_SIZE = 8192 LENGTH 10000 PAGES DEFAULT CHARACTER SET UTF8 FILE 'D:\test.fdb2' FILE 'D:\test.fdb3' STARTING AT PAGE 20001; информацию о состоянии шифрования. Например, следующий запрос select MON$CRYPT_PAGE * 100 / MON$PAGES from MON$DATABASE будет отображать процент завершения процесса

localhost:employee Owner: SYSDBA PAGE_SIZE 8192 Number of DB pages allocated = 346 Number of DB pages used = 310 Number of DB pages free = 36 Sweep interval = 20000 Forced Writes are OFF Transaction

утеряно ко- мандами "delete from xxx" и последующей "ой!", чем продуманной командой "delete from rdb $pages". —Jim Starkey Использование транзакций В СУБД Firebird в DSQL (dynamic SQL) транзакции «напрямую» возможность получать доступ к базам данных СУБД Firebird из таких сред, как Visual Basic или ActiveX Server Pages (ASP). В настоящее время наиболее популярной является собственная связка Microsoft - OLE DB->ODBC

are stored in the RDB$GENERATORS system table. Their values however are stored in special reserved pages inside the database. You never touch those values directly; you access them by means of built-in a contiguous series of IDs. Depending on the situation, the restored database may also need less pages for the generator values. Dropping generators in old IB and Firebird versions InterBase 6 and earlier