. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6.3. Automatic Two-phase Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 10.4. Disabling Automatic Sweeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . option has been shown above under listing limbo transactions. 6.3. Automatic Two-phase Recovery Gfix can be used to perform automatic two-phase recovery. The command for this is -⁠tw[o_phase] and, like

foreign key index) or RDB$n (for a unique key index). Again, n represents one or more digits. Automatic naming of table-level constraints and their indexes follows the same pattern, unless the names command-line tools have been supplied with switches that an administrator can use to suppress the automatic firing of database triggers. So far, they are: gbak -nodbtriggers isql -nodbtriggers nbackup -T Natural joins Taking the idea of the named columns join a step further, a natural join performs an automatic equi-join on all the columns that have the same name in the left and right table. The data types

co-administrators and SYSDBA • Co-admins can create, alter and drop users, but contrary to SYSDBA they have no automatic privileges in regular databases. • Unlike SYSDBA, co-admins must specify the RDB$ADMIN role explicitly little or no Firebird knowledge mess up databases or user accounts. If you still want to apply the automatic SYSDBA mapping as it was in Firebird 2.1, login as SYSDBA and give the command: create global from predefined_group domain_any_rid_admins to user sysdba This grants all Windows administrators automatic SYSDBA rights in every database (including the Chapter 5. Server configuration and management

foreign key index) or RDB$n (for a unique key index). Again, n represents one or more digits. Automatic naming of table-level constraints and their indexes follows the same pattern, unless the names command-line tools have been supplied with switches that an administrator can use to suppress the automatic firing of database triggers. So far, they are: gbak -nodbtriggers isql -nodbtriggers nbackup -T Natural joins Taking the idea of the named columns join a step further, a natural join performs an automatic equi-join on all the columns that have the same name in the left and right table. The data types

have a compelling need to run the server as an application, choose service. Manual or automatic? With the automatic option, Firebird will start up whenever you boot the host machine. With the manual option

Windows NT/2000/XP only: If InterBase and/or Firebird is installed as a service, disable the automatic service startup both for the service itself and for the Guardian service. To do this, you can use

Administrator accounts to automatically have full access to the user management functions. The automatic mapping can be revoked as follows: SQL> SQL> alter role rdb$admin drop auto admin mapping; SQL>

record versions that are no longer required and this is usually covered by a sweep — manual or automatic — or by a full table scan of any affected table. As gbak accesses all the rows in the tables being

SQL prompt in two ways: ◦ When COMMIT statements are included in the script. ◦ By ensuring the automatic commit of DDL in a isql script, by issuing a SET AUTODDL ON statement. To turn it off, issue a