Converting a database to case control

SQL server databases without database replication can be converted to case-controlled databases. This allows copies of the data to be used remotely without connection and synchronized when connection is available.

About this task

Turning on case control is an irreversible process. Ensure that you back up your database before you experiment with this facility on a database that contains data. Where there is no data yet, you might create a template from your database instead of backing up.

After you convert to case control:

  • You cannot convert the database back to standard (SCC) control.
  • Menu commands and options that apply to security classification (SC) codes and SCC lists are no longer available.
  • Any records that are classified by using security classification codes are stripped of those codes and assigned to a default case.
Note: You can preserve the classifications represented by security classification codes, for example to place Confidential records in a separate case to other records. Before you turn on case control, you would need to export the Confidential records that you want to allocate to a different case. If required, you can delete those records from the database - this means that the Confidential records will not become part of the default case. After the database is case controlled, import the Confidential records into the required case(s).


To convert an existing database to case control:
  1. If you have an Access database, convert the database to SQL Server format.
    For more information, see Upsizing a Database to SQL Server.
  2. Select File > Database Properties.
  3. On the Advanced page, select Case Control and click OK.
    Note: This option is not available if iBase database replication is installed on the machine.
  4. Confirm that you want to proceed with the conversion to case control and the removal of existing SC codes and SCC lists.
  5. Enter the name of the default case. All existing records, folder objects, and alert definitions will be moved to this case.
    You can use export and import to move records between cases.
  6. If alerting is in use, assign all users who have created alert definitions to the default case. You must do this before you close the database.
    Warning: Alert definitions without owners are deleted when you close the database.