| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Existing application databases can be cloned by selecting the Clone button in the database administration screen, accessed from the Administration module. Cloning a database creates a copy of the application database, not of the physical SQL server databases. For an explanation of the difference between these two types of databases see Managing databases.
This feature allows sophisticated user access restrictions to be applied, where the same physical database is made accessible to a user multiple times but with different levels of restriction.
Because the cloned application database refers to the same physical database, both of them are updated at the same time when the physical database is updated by Vacuum.
When cloning an existing database, the following options apply, as shown in the image below:
- Display Name: The new display name for the database - this is the name users see in the Home screen.
- Copy: By default, Defined Periods: All the defined periods , existing users and default restriction are all copies copied across to the new database. You can optionally also copy personal favorites and favorite folders.
- Users: All existing users and their current default period and user restriction restrictions are copied to the new database.
- Default Restriction: If the source database has a default restriction, it is copied to the new database.
- Folder Favorites: All existing global favorites, stored in folders against the source database are replicated on the new one.
- Personal Favorites: All existing personal favorites created by users on the source database are replicated on the new one.
- Design: Allows users to edit the design of the clone in Designer. To do this, it creates a physical copy of the database and breaks the link between original and clone - more detail below.
By default, the defined periods, existing users and default restriction are all copied across to the new database. You can optionally also copy personal favorites and favorite folders.
Clone produces different results depending on whether Design is ticked:
Clone without Design
If Design is not ticked, cloning a database creates a copy of the application database, not of the physical SQL server databases. For an explanation, see Managing databases. This feature allows sophisticated user access restrictions to be applied, where the same physical database is made accessible to a user multiple times but with different levels of restriction.
- A permanent link is retained between the original and the clone. Edit the original, and the clone will also be edited.
- Because the cloned application database refers to the same physical database, both of them are updated at the same time when the physical database is built.
- Users won't be able to edit the cloned database in Designer.
Clone with Design
If Design is ticked, then a physical copy of the SQL server database is created.
- No link is retained between the original and the clone. The clone becomes a completely separate database.
- Users can use the Designer tool to modify the design of the cloned database.
| Info | ||
|---|---|---|
| ||