5.1.1. CREATE DATABASE

    Used for

    Creating a new database

    Available in

    DSQL, ESQL

    Syntax

    The CREATE DATABASE statement creates a new database. You can use CREATE DATABASE or CREATE SCHEMA. They are synonymous.

    A database may consist of one or several files. The first (main) file is called the primary file, subsequent files are called secondary file[s].

    Multi-file Databases

    Nowadays, multi-file databases are considered an anachronism. It made sense to use multi-file databases on old file systems where the size of any file is limited. For instance, you could not create a file larger than 4 GB on FAT32.

    The primary file specification is the name of the database file and its extension with the full path to it according to the rules of the OS platform file system being used. The database file must not exist at the moment when the database is being created. If it does exist, you will get an error message and the database will not be created.

    If the full path to the database is not specified, the database will be created in one of the system directories. The particular directory depends on the operating system. For this reason, unless you have a strong reason to prefer that situation, always specify the absolute path, when creating either the database or an alias for it.

    Using a Database Alias
    1. alias = filepath
    Creating a Database Remotely

    If you create a database on a remote server, you should specify the remote server specification. The remote server specification depends on the protocol being used. If you use the TCP/IP protocol to create a database, the primary file specification should look like this:

    1. _servername_[/{_port_|_service_}]:{_filepath_ | _db_alias_}

    If you use the Named Pipes protocol to create a database on a Windows server, the primary file specification should look like this:

    1. \\servername\{filepath | db_alias}
    Optional Parameters for CREATE DATABASE

    USER and PASSWORD

    Clauses for specifying the user name and the password, respectively, of an existing user in the security database security2.fdb. You do not have to specify the username and password if the ISC_USER and ISC_PASSWORD environment variables are set. The user specified in the process of creating the database will be its owner. This will be important when considering database and object privileges.

    PAGE_SIZE

    Clause for specifying the database page size. This size will be set for the primary file and all secondary files of the database. If you specify the database page size less than 4,096, it will be changed automatically to the default page size, 4,096. Other values not equal to either 4,096, 8,192 or 16,384 will be changed to the closest smaller supported value. If the database page size is not specified, it is set to the default value of 4,096.

    LENGTH

    Clause specifying the maximum size of the primary or secondary database file, in pages. When a database is created, its primary and secondary files will occupy the minimum number of pages necessary to store the system data, regardless of the value specified in the LENGTH clause. The LENGTH value does not affect the size of the only (or last, in a multi-file database) file. The file will keep increasing its size automatically when necessary.

    SET NAMES

    Clause specifying the character set of the connection available after the database is successfully created. The character set NONE is used by default. Notice that the character set should be enclosed in a pair of apostrophes (single quotes).

    DEFAULT CHARACTER SET

    Clause specifying the default character set for creating data structures of string data types. Character sets are applied to CHAR, VARCHAR and BLOB TEXT data types. The character set NONE is used by default. It is also possible to specify the default COLLATION for the default character set, making that collation sequence the default for the default character set. The default will be used for the entire database except where an alternative character set, with or without a specified collation, is used explicitly for a field, domain, variable, cast expression, etc.

    STARTING AT

    Clause that specifies the database page number at which the next secondary database file should start. When the previous file is completely filled with data according to the specified page number, the system will start adding new data to the next database file.

    DIFFERENCE FILE

    Clause specifying the path and name for the 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, see ALTER DATABASE.

    SET SQL DIALECT

    Databases are created in Dialect 3 by default. For the database to be created in SQL dialect 1, you will need to execute the statement SET SQL DIALECT 1 from script or the client application, e.g. in isql, before the CREATE DATABASE statement.

    Examples Using CREATE DATABASE

    1. Creating a database in Windows, located on disk D with a page size of 8,192. The owner of the database will be the user wizard. The database will be in Dialect 1 and it will use WIN1251 as its default character set.

      1. SET SQL DIALECT 1;
      3. USER 'wizard' PASSWORD 'player'
      4. PAGE_SIZE = 8192 DEFAULT CHARACTER SET WIN1251;

    2. Creating a database in the Linux operating system with a page size of 4,096. The owner of the database will be the user wizard. The database will be in Dialect 3 and it will use UTF8 as its default character set, with UNICODE_CI_AI as the default collation.

      1. CREATE DATABASE '/home/firebird/test.fdb'
      2. USER 'wizard' PASSWORD 'player'
      3. DEFAULT CHARACTER SET UTF8 COLLATION UNICODE_CI_AI;

    3. Creating a database on the remote server “baseserver” with the path specified in the alias “test” that has been defined previously in the file aliases.conf. The TCP/IP protocol is used. The owner of the database will be the user wizard. The database will be in Dialect 3 and will use UTF8 as its default character set.

    4. Creating a database in Dialect 3 with UTF8 as its default character set. The primary file will contain up to 10,000 pages with a page size of 8,192. As soon as the primary file has reached the maximum number of pages, Firebird will start allocating pages to the secondary file test.fdb2. If that file is filled up to its maximum as well, test.fdb3 becomes the recipient of all new page allocations. As the last file, it has no page limit imposed on it by Firebird. New allocations will continue for as long as the file system allows it or until the storage device runs out of free space. If a LENGTH parameter were supplied for this last file, it would be ignored.

      1. SET SQL DIALECT 3;
      2. USER 'wizard' PASSWORD 'player'
      3. PAGE_SIZE = 8192
      4. DEFAULT CHARACTER SET UTF8
      5. FILE 'D:\test.fdb2'
      6. STARTING AT PAGE 10001
      7. FILE 'D:\test.fdb3'
      8. STARTING AT PAGE 20001;

    5. Creating a database in Dialect 3 with UTF8 as its default character set. The primary file will contain up to 10,000 pages with a page size of 8,192. As far as file size and the use of secondary files are concerned, this database will behave exactly like the one in the previous example.

      1. SET SQL DIALECT 3;
      2. CREATE DATABASE 'baseserver:D:\test.fdb'
      3. USER 'wizard' PASSWORD 'player'
      4. PAGE_SIZE = 8192
      5. LENGTH 10000 PAGES
      6. DEFAULT CHARACTER SET UTF8
      7. FILE 'D:\test.fdb2'
      8. FILE 'D:\test.fdb3'
      9. STARTING AT PAGE 20001;

    See also

    ALTER DATABASE,

    5.1.2. ALTER DATABASE

    Used for

    Altering the file organisation of a database or toggling its “copy-safe” state

    Available in

    DSQL — both functions. ESQL — file reorganisation only

    Syntax

    1. ALTER {DATABASE | SCHEMA}
    2.   [<add_sec_clause> [<add_sec_clause> ...]]
    3.   [ADD DIFFERENCE FILE 'diff_file' | DROP DIFFERENCE FILE]
    4.   [{BEGIN | END} BACKUP]
    6. <add_sec_clause> ::= ADD <sec_file> [<sec_file> ...]
    8.   FILE 'filepath'
    9.   [STARTING [AT [PAGE]] pagenum]
    Table 17. ALTER DATABASE Statement Parameters
    ParameterDescription

    add_sec_clause

    Adding a secondary database file

    sec_file

    File specification for secondary file

    filepath

    Full path and file name of the delta file or the secondary database file

    pagenum

    Page number from which the secondary database file is to start

    Maximum size of the secondary file in pages

    diff_file

    File path and name of the .delta file (difference file)

    The ALTER DATABASE statement can:

    • add secondary files to a database

    • switch a single-file database into and out of the “copy-safe” mode (DSQL only)

    • set or unset the path and name of the delta file for physical backups (DSQL only)

    Only have the authority to use ALTER DATABASE.

    Parameters for ALTER DATABASE

    ADD FILE

    Adds a secondary file to the database. It is necessary to specify the full path to the file and the name of the secondary file. The description for the secondary file is similar to the one given for the CREATE DATABASE statement.

    ADD DIFFERENCE FILE

    specifies the path and name of the delta file that stores any mutations to the database whenever it is switched to the “copy-safe” mode. This clause does not actually add any file. It just overrides the default name and path of the .delta file. To change the existing settings, you should delete the previously specified description of the .delta file using the DROP DIFFERENCE FILE clause before specifying the new description of the delta file. If the path and name of the .delta file are not overridden, the file will have the same path and name as the database, but with the .delta file extension.

    DROP DIFFERENCE FILE

    This is the clause that deletes the description (path and name) of the .delta file specified previously in the ADD DIFFERENCE FILE clause. The file is not actually deleted. DROP DIFFERENCE FILE deletes the path and name of the .delta file from the database header. Next time the database is switched to the “copy-safe” mode, the default values will be used (i.e. the same path and name as those of the database, but with the .delta extension).

    BEGIN BACKUP

    This is the clause that switches the database to the “copy-safe” mode. ALTER DATABASE with this clause freezes the main database file, making it possible to back it up safely using file system tools, even if users are connected and performing operations with data. Until the backup state of the database is reverted to NORMAL, all changes made to the database will be written to the .delta (difference) file.

    Despite its syntax, a statement with the BEGIN BACKUP clause does not start a backup process but just creates the conditions for doing a task that requires the database file to be read-only temporarily.

    END BACKUP

    This is the clause used to switch the database from the “copy-safe” mode to the normal mode. A statement with this clause merges the .delta file with the main database file and restores the normal operation of the database. Once the END BACKUP process starts, the conditions no longer exist for creating safe backups by means of file system tools.

    Examples of ALTER DATABASE Usage

    1. Adding a secondary file to the database. As soon as 30000 pages are filled in the previous primary or secondary file, the Firebird engine will start adding data to the secondary file test4.fdb.

      1. ALTER DATABASE
      2.   ADD FILE 'D:\test4.fdb'
      3.     STARTING AT PAGE 30001;

    2. Specifying the path and name of the delta file:

    3. Deleting the description of the delta file:

      1. ALTER DATABASE
      2.   DROP DIFFERENCE FILE;

    4. Switching the database to the “copy-safe” mode:

      1. ALTER DATABASE
      2.   BEGIN BACKUP;

    5. Switching the database back from the “copy-safe” mode to the normal operation mode:

      1. ALTER DATABASE
      2.   END BACKUP;

    See also

    CREATE DATABASE,

    5.1.3. DROP DATABASE

    Used for

    Deleting the database to which you are currently connected

    Available in

    DSQL, ESQL

    Syntax

      The DROP DATABASE statement deletes the current database. Before deleting a database, you have to connect to it. The statement deletes the primary file, all secondary files and all .

      Only administrators have the authority to use DROP DATABASE.

      Example

      Deleting the database the client is connected to.

      1. DROP DATABASE;

      See also

      , ALTER DATABASE