Use the context menu of a server alias

The following table lists the functionalities that are available when you right-click a server alias in the explorer.

For some functionalities it is necessary to establish a connection to the Alfabet database by first selecting Connect... in the context menu. The table also specifies whether a connection is required to use a functionality.

If an action modifies the database content or the alfabetMS.xml configuration file, this is also specified in the table.

When you select a functionality from the context that establishes a connection to the Alfabet database, a login window pops up. You must enter the user name and password defined for login to the Alfabet database.

When Windows sign-on is configured for connections to the Alfabet database, click OK without entering a user name and password. The Alfabet Administrator will connect to the Alfabet database via Windows sign-on and perform the selected operation.

The most important functionalities are listed in the following table.

Select...	In Order To....	Database connection required
Connect	Establish a connection to the database that is specified in the server alias configuration.	This action establishes a connection to the Alfabet database. Login to the database is required.
Disconnect	Close an existing connection to the Alfabet database configured in the server alias.	Yes, via the Connect functionality in the context menu.
Create the Alias as Copy	Create a new server alias configuration with the same attribute settings as the current server alias configuration. The attribute settings of the new server alias can then be modified as needed.	No
Archive Current Database	Create an ADBZ archive file of the Alfabet database that this server alias connects to. An Include Audit option allows audit tables to be excluded from restore. Deselection of audit can solve restore issues with very large databases. A Squeeze Audit Tables option is available that scans the audit tables prior to archiving the database. Any entries that were generated during, for example, a batch update of data via batch utilities where no audit-relevant changes were documented will be deleted from the audit tables prior to archiving the database. The Include User Settings option allows user settings to be added to the archive that are defined for the current database.	Yes, via the Connect functionality in the context menu.
Restore Database Archive	Restore an ADBZ archive or an ADB archive file of an Alfabet database in the database that this server alias connects to. Please note the following: This action overwrites the content of the Alfabet database. Never restore a database without prior backup of the current database! If the restore action fails, it may result in a corrupt database! The restore of a database will fail if the server alias is configured to enforce password criteria and the database in the ADBZ file contains users with empty passwords or with a password not matching the defined user password criteria. If restore of the database fails, the target database may be corrupt. This mechanism is only available if the database server is installed on the same machine as the Alfabet Administrator. It is not intended for use in productive environments and should only be used to ease database maintenance in development or test environments. Prior to using this functionality, ensure that no Alfabet components are currently connected to the Alfabet database. This includes the Alfabet Web Application, the Alfabet Server (service), Alfabet Expand or batch utilities. An Include Audit option allows entries in audit tables stored in the ADBZ file to be excluded from restore and audit tables are created without content in the target database. Deselection of audit can solve restore issues with very large databases. A Squeeze Audit Tables option is available that scans the audit tables for obsolete entries. Any entries that were generated during, for example, a batch update of data via batch utilities where no audit-relevant changes were documented will be deleted from the audit tables restored from the ADBZ file.	This action establishes a connection to the Alfabet database automatically as part of the action. Login to the database is required.
Archive Current Database With Anonymized Data	Anonymize all values for all object class properties configured to be anonymized in the Alfabet meta-model in a database archive file (ADBZ) during creation of the archive file. The data in the original Alfabet database that is archived is not affected. This method is useful to archive the content of a productive database in an anonymized form to implement it in a test or development environment without information about sensitive data.	Yes, via the Connect functionality in the context menu.
Anonymize Data	Anonymizes all values for all object class properties configured to be anonymized in the Alfabet meta-model of the current Alfabet database. Note: Anonymizing data might disrupt database integrity. It cannot be reverted! Always back up the Alfabet database prior to triggering data anonymization!	This action establishes a connection to the Alfabet database automatically as part of the action. Login to the database is required.
Anonymize User Data	Anonymize data for one or multiple selected users (for one or multiple selected objects of the object class Person). Data for a selected user is only anonymized if anonymization is enabled in the configuration of the object class Person and if the user is not explicitly excluded from anonymization. Note: Anonymizing data might disrupt database integrity. It cannot be reverted! Always back up the Alfabet database prior to triggering data anonymization!	Yes, via the Connect functionality in the context menu.
Release Restricted Mode	During update of the meta-model and during restore of the database, the Alfabet database is set to a restricted mode and connections to other Alfabet components are closed and new connection cannot be re-established. If the restricted mode is not automatically released after the change to the Alfabet database has been performed, the restricted mode can be released by using this option.	No
Activate Audit	Activates the history tracking for the Alfabet Web Application connecting to the Alfabet database with this server alias. If history tracking is activated, changes to objects will be documented in audit tables in the Alfabet database for all object classes that are configured to be audited. .	Yes, via the Connect functionality in the context menu.
Deactivate Audit	Deactivates the history tracking for the Alfabet Web Application connecting to the Alfabet database with this server alias. If history tracking is deactivated, changes to objects will not be documented in the audit tables in the Alfabet database. .	Yes, via the Connect functionality in the context menu.
Execute Script	Execute a script delivered from Software GmbH Support. NOTE: This action can modify the content of the Alfabet database.	Yes, via the Connect functionality in the context menu.
Update Meta-Model	Replace or merge the customer configuration of the solution environment of the current database with the customer configuration saved to an .amm update file. NOTE: This action can modify the content of the Alfabet database. Always back up the target database prior to performing an update of the meta-model.* NOTE: Prior to using this functionality, ensure that no Alfabet components are currently connected to the Alfabet database. This includes the Alfabet Web Application, the Alfabet Server (service), Alfabet Expand, a connected server alias in the Alfabet Administrator or batch utilities.	This action establishes a connection to the Alfabet database. Login to the database is required. Please note that this functionality is not available if the alias is connected via the Connect functionality in the context menu.
Create Configuration Meta-Model Update File	Save the customer configuration of the solution environment of the current database to an *.amm update file. .	Yes, via the Connect functionality in the context menu.
Update Assembly	Update the solution assembly from a DLL file (for example, for a new patch release). This is normally executed by Software GmbH Support. NOTE: This action modifies the content of the Alfabet database.	Yes, via the Connect functionality in the context menu.
Check SMTP	Test the connection to the SMTP server for outgoing mail from the Alfabet Server.	Yes, via the Connect functionality in the context menu.
Register Event Logger	Registers the Alfabet component with the Windows® Event Log. After registration, login and logout actions are written to the Windows Event Log. Registration requires a specific configuration of the Alfabet component prior to performing the registration.	No