Databases

You can view or edit database properties, and manage Display Names on the Databases page in the MI Admin Schema tool.

Note: To add or remove databases, and monitor database health, use the MI Server Manager tool.
  1. Open the MI Admin Schema tool and click Edit Database in the panel on the left of the window to open the Databases page.
  2. Select a database and then click Edit to view or edit its properties.
  3. Make any changes you need:
    OptionDescription
    Database name

    All of the databases in your Granta MI system must have a different name.

    • May contain up to 255 characters.
    • May not start or end with a space character.
    Default Table Specifies the Table into which data will be imported when doing a command-line import to the database, if no Table is specified in the command-line arguments.
    Database currency Specifies the database currency, allowing users to work in a currency that is different from the Granta MI system currency when viewing and modifying monetary data, such as material price. For more information, see Database currency.
    Display Names Display Names can be used to define alternative names for some schema objects, for example, in a different language from the underlying schema object name. For more information, see Display Names.
    Database version GUID This GUID is used to uniquely identify the database in cross-database Tabular column links. Click New GUID to change it, if required.
    Note: If you change the database version GUID, any existing cross-database Tabular links to this database will continue to reference the original database version GUID, and so those links will no longer work.
    Author, Company, Notes

    Optional database properties may be used for specifying in-house information or notes about the database.

    Author's name and Author's company are limited to 255 characters.

    Notes can be up to 1048576 characters.
    Retarget tabular attributes

    Where this database is a target for existing cross-database Tabular links, you can use Retarget tabular attributes to specify a different target database for those links.

    This can be used, for example, to ensure that if you replace a target database with a newer edition of the same database, existing cross-database Tabular links will be re-targeted to the new database.