. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 MON$MEMORY_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . how to back up a database in two quite different ways and how to switch the database to the “copy-safe” mode for performing an external backup safely. 5.1.1. CREATE DATABASE Used for Creating a new file delta that stores any mutations to the database file after it has been switched to the “copy-safe” mode by the ALTER DATABASE BEGIN BACKUP statement. For the detailed description of this clause,

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757 MON$MEMORY_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . how to back up a database in two quite different ways and how to switch the database to the “copy-safe” mode for performing an external backup safely. 5.1.1. CREATE DATABASE Used for Creating a new wasted space of a 3KB blob on page size 4096 with one on 32768: +/- 1KB vs +/- 29KB), and increase memory consumption of the page cache. LENGTH Clause specifying the maximum size of the primary or secondary

........................................................................................ 696 MON$MEMORY_USAGE .......................................................................................... записываться изменения, внесённые в БД после перевода её в режим «безопасного копирования» («copy-safe») путём выполнения команды ALTER DATABASE BEGIN BACKUP. Полное описание данного параметра см. в ALTER записываться изменения, внесённые в базу данных после перевода её в режим «безопасного копирования» («copy-safe»). Этот оператор в действительности не добавляет файла. Он просто переопределяет умалчиваемые имя

access rights to the database file. Local connections On Windows, both architectures now support safe and reliable local connec- tions, with only the server process requiring access rights to the database Install Superserver first; • Copy the applet Firebird2Control.cpl from the Windows system folder to a safe place; • Uninstall Superserver; • Install Classic; • Copy the applet back to the system directory configure a database to use asynchronous data writes – whereby modified or new data are held in the memory cache for periodic flushing to disk by the operating system's I/O subsystem. The common term for

make direct local connections, but these are not as fast as the “Classic” ones on Linux and also less safe. Server must run as root. This poses a risk if the server were to be hacked or contained a severe Superserver, without using the TCP/IP loop- back. This is not a TCP/IP connection and it is not a thread-safe way to connect to a local server. For using single instances of the command-line tools (gsec, gbak contrast, direct database connections - even multiple - under a Linux Classic server are completely safe. Firebird 1.0 Quick Start Guide 11 Default user name and password The SYSDBA user has all privileges

allocated to store (cache) database pages in memory to help improve the efficiency of the database performance. It is far quicker to read data from memory that it is to have to physically read the data that subsequently failed, for example, when the application aborted. In this case, committed data is safe but uncommitted data will have been rolled back. The page appears to have been allocated for use Database Write Mode Many operating systems employ a disk cache mechanism. This uses an area of memory (which may be part of your server’s overall RAM or may be built into the disk hardware) to buffer

expressions that contain NULL or may resolve to NULL. If you only need a quick reference to refresh your memory, go to the summary at the end of the guide. So — what is it? In SQL, NULL is not a value. It is its declaration to see how values are passed and returned. If it says “by descriptor”, it should be safe (though it never hurts to make sure). Ditto if arguments are followed by a NULL keyword. In all other until now it works in practice, this may not be the case in future versions. It’s better to stay safe and use the SQL given above. 15.2.2. Adding a CHECK constraint to an existing column To add a CHECK

always affect the accounts in the security database that governs that specific database. To be on the safe side, you may want to connect to the security database itself before issuing your user management connection is attempted (by the Loopback provider), in this order: 1. On Windows: using XNET (shared memory) on the local machine; 2. Using TCP/IP via localhost. You can force Firebird to use a certain protocol configure a database to use asynchronous data writes — whereby modified or new data are held in the memory cache for periodic flushing to disk by the operating system’s I/O subsystem. The common term for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681 MON$MEMORY_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sekundärdateien zu einer Datenbank hinzufügen • Umschalten einer Einzeldatei-Datenbank in den “copy-safe”-Modus (nur DSQL) • Pfad und Name der Delta-Datei für physische Backups setzen oder aufheben (nur Namen der .delta-Datei aus dem Datenbank-Header. Wenn die Datenbank das nächste Mal in den “copy-safe”-Modus geschaltet wird, werden die Standardwerte verwendet (d. h. der gleiche Pfad und Name wie die

Introduction 2 Chapter 2. Generator Basics 2.1. What is a generator? Think of a generator as a “thread-safe” integer counter that lives inside a Firebird database. You can create one by giving it a name: server side, after you send the Insert statement from the client. This plainly means there is no safe way to know from the client side which ID was generated for the row you just inserted. You could from the “outside”. Although this can be very handy, it has a strong limitation: it’s not multi-user safe. If the SP would run simultaneously in two transactions, they would mess up the progress generator