Configuring and maintaining databasesYou can create and maintain iBase databases, whether in Microsoft™ Access or SQL Server format.Create databasesYou can create different types of iBase database for operational use.Database subsetsA database subset is a portion of records in the database that are copied into a separate database. This collection of records are selected by creating a database subset definition that consists of the results of queries and sets.Creating case-controlled databasesIf you need to restrict access to data on a case by case basis, you must to create a case-controlled database. Because you cannot convert a case-controlled database to a standard (SCC) controlled database, consider carefully whether you require this facility.Routine maintenanceThere are several areas in iBase that require routine maintenance to ensure that your database continues to run correctly. Where possible, you can use tools that are provided in iBase Designer to run maintenance tasks.Batch deleteUsers can delete records from the database either individually or in batches. When an entity record is deleted, all links to that entity are also deleted - the link end entities are not deleted.Backing up iBaseLike any critical system, it's important to make and maintain regular backups of your iBase databases. This part of the documentation describes how and when to make backups, and provides guidance on establishing a backup policy.Moving and Copying DatabasesThe procedures used to move and copy databases are slightly different for Microsoft Access and SQL Server databases. The principles of moving a database applies equally to copying a populated database. Database schema updatesSchema changes to an operational database on a server are typically made and tested in a temporary copy of the database before application to the operational database itself. You can use the Update Database Schema command in iBase Designer to manage this process, making the changes and then applying them to the other databases by applying a new database template.Common folder objectsYou can simplify the administration of several common databases, by defining a core set of folder objects (common folder objects).Checking a databaseYou can check a database after upsizing, or after large changes or prolonged editing, or at any time that you suspect problems.Managing SQL Server databasesiBase provides the capabilities to store data in Microsoft™ SQL Server databases and Microsoft Access databases. Microsoft Access should be used as the supporting database only if the number of simultaneous users is five or less. When a database of more than 200 Mb is accessed by a number of users simultaneously then consideration should be given to using SQL Server.Parent topic: Managing i2 iBase
