Creating a security file
In order to control access to your iBase database, you must create a security file. You use the security file to control who can access the iBase and iBase Designer applications, and any iBase databases secured by the security file.
About this task
Try to avoid creating multiple security files. You can provide groups with varied but restricted access to many databases secured by the same security file.
To create your own security file, you must first create or choose a folder to hold it. Only one security file can be created in each folder, but you can create subfolders to hold security files if required.
A good strategy is to create a shared folder on a server machine with high availability to all likely users. All users of a database must have access to the folder to log on and open databases.
The default location for the database or the database connection file is the same folder as the security file.
- For Access databases, you must allow enough disk space to hold the database files (Access databases are limited to 2 Gb).
- For SQL Server databases, the database files that are held in the folder with the security file are connection files that hold only enough administrative data to allow connection to the SQL Server database system. These connection files are much smaller than full databases, typically in the range 50 kilobytes through 1 MB. Full use of iBase facilities imposes some other requirements on the machine that is running SQL Server.
Procedure
What to do next
- Create groups and users. For more information, see Creating Groups and Adding Members.
- Change the administrative password. See Changing the administrative password.
After you create a security file, you must give authorized users access to it at the Windows™ level, and also protect it from accidental deletion.
You must also include it in any backup schedules for the database. For more information, see iBase backup policies.