Creating an SQL Server security file

You always create security files in Microsoft™ Access format and then convert them to SQL Server. The main reason for converting to this format is to increase the security of your security data.

Before you begin

The conversion leaves a security connection file (the .ids file) in the iBase database folder and creates a SQL Server database with the name <file>_Sec on the designated server (where <file> is the name of the ids file). Users connect to the SQL Server database by logging on to the connection file. The connection file holds just the information necessary to allow the user to connect to the SQL Server instance.

Note: If you copy security connection files to client machines, it might compromise the security of your system and adds to the administrative workload. You should keep the connection file, in the same folder as the database connection file, in a central location. If it becomes necessary to copy it, then the file name and path must be identical on each machine to which you copy it.

About this task

For SQL Server databases, the name of the security file is used to generate the name of the SQL Server database so you might want to discuss the naming convention to use with your SQL Server administrator and, if necessary, rename the security file before you upsize it. Although, you can always rename a security connection file, you cannot rename the associated SQL Server database. See SQL Server Database Names for details.

Procedure

To upsize a security file:

  1. Using iBase Designer, log on as a security or system administrator using the Microsoft Access security file you want to convert.

  2. Click Cancel at the prompt to create or open a database.

  3. Select Tools > Database Setup Upsize Security File to SQL Server.

  4. Click OK when you are informed that a backup has been made. This is a backup of the original Microsoft Access security file and has the file extension .ids.bak (appended with a number, such as .ids.bak1, if there is already a file with this extension in the folder).

  5. In the Upsize Security File dialog, enter the server name. Do not select the Local option from the Server list.

  6. Select the security mode as directed by your SQL Server administrator.

  7. Skip the Identifier field - identifiers for security files are only used in iBase database replication.

  8. Click OK to validate the settings and perform the upsize, then click OK when the upsize is complete. If you want to review the connection details and ID of the security connection file, select File Security File Properties. The path of the security connection file will also be displayed in the status area with (SSE) after the file name to indicate that it is SQL Server format.

  9. Back up the connection file (.ids file). If you lose the connection file, you are not able to connect to the SQL Server database.

What to do next

You can protect the SQL Server security connection file by making it read-only or by setting appropriate security permissions.

This will allow any user in iBase Designer to view the properties of the connection file but prevents anyone, including iBase administrators, from changing the SQL Server connection details. This applies to SQL Server files only.

You should also ensure that the security connection file is included in any backup schedules for the database folder. For more information, see Backing Up iBase Databases.