Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Existing application databases can be cloned by selecting the Clone button in the database administration screen, accessed from Administration > Databases.

When cloning an existing database, the following options are available, as shown in the image below:

  • Display Name: The new display name for the database - this is the name users see in the Homepage (old experience).
  • Defined Periods: All the defined periods are all copied across to the new database.
  • Users: All existing users and their current default period and user restrictions are copied to the new database. This option only becomes available once 'Defined periods' is checked.
  • 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.

Clone without Design

 

Clone produces different results depending on whether Design is ticked.

 

If Design is not ticked, cloning a database creates a copy of the application database, not of the physical SQL server 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.



  • No labels