SQL Server database names

The names that you choose for the security (ids) file and database (idb) file in iBase are used to generate the names of the SQL Server databases. For this reason, you might want to discuss the naming convention to use with your SQL Server administrator.

Main iBase database

A complete logical iBase database (for entity and link data) contains two Microsoft™ SQL Server databases:

  • An iBase database:

    Typically the database name is similar to the name of the connection file, but is subject to modification to comply with SQL Server naming rules.

    The database name always contains an underscore ( _ ). For example, if the requested database name is Intelligence, SQL Server uses the name Intelligence_ and the connection file remains Intelligence.idb. Additionally, any spaces in database names are replaced by underscores (_). T

  • An Audit Log database:

    The Audit Log database is the database name with _log added at the end, for example Intelligence__log. (Notice the double underscore in this single-word database name.)

These two databases are always present.

iBase security database

Optionally, iBase security data can be held in an SQL Server database. The SQL Server name follows the rules for the main iBase database but is appended with _sec. For example, if the name of the Access security file is Intelligence.ids then the SQL Server name is Intelligence__sec.

Renaming SQL Server databases

To rename an SQL Server database that contains entity and link data (not security data), create a new database in iBase Designer with the wanted name. The name must uniquely identify the database within your iBase system and also when used with third-party iBase databases. You must be logged on to the correct security file when you do rename a database. The connection file that is required by iBase to connect to the database on the server is also created. To move the data to the new database, your SQL Server administrator must make a backup of the SQL Server database that you want to rename and then restore the backup over the new database.

Attention: You cannot rename an SQL Server security database in this way. You lose the connection between the security file and the databases that it secures and prevent your users from opening the databases.