Database Tables

• About table registration
  Registering database tables gives the system access to the database tables during processing.
• Create database tables
• Register database tables
  You must register a database table before creating an app or publishing an app that has been imported. You can also complete this procedure to re-register a modified database table in order for the system to recognize the modifications. It is not necessary to undo the table registration before re-registering it.
• Use one table's connection details to register another table
  You can use a table's connection information to register another table. If you are using the same connection, this is a quick way to register additional tables without re-entering the connection details.
• Add a secondary source
  Adding a secondary database source is the first step in configuring a database connectivity fail-over recovery. Using error-handling rules, the system can switch between the primary and secondary database tables in case of system network error or database connectivity failure. Database fail-over is intended for download requests from read-only databases. When database fail-over occurs, records on the secondary database are available for use with download requests. This function is not available for System Tables.
• View table information
  You can view details about a registered database table that include the name, the database name and owner, and connection information.
• Manage table data
• Unregister tables
  You can unregister a non-system database table regardless of whether it is referenced by an app. Note that an app will not publish if it references a table that is not registered. If a table is already registered, but you need to re-register it because of modifications or use with another app, you do not need to unregister the table before re-registering it.
• Requirements for download requests and marking records
  When creating a database table to be used in a download request that requires records to be marked to indicate use at the device, fields must also be assigned to hold the record status, device name, and call ID (applicable to SQL Server databases) specific to the environment.