Boomerang tables are integral part of Boomerang Services system. All Boomerang tables are located in Boomerang catalog and feature dbo schema. Boomerang background services use Windows authentication for SQL server connection.
Any changes to Boomerang tables, including, but not limited to, adding new or altering existing columns and index objects, adding table and/or column constraints, altering table and column collations, etc. are not advisable
The ownership to Boomerang tables should not be removed from designated Boomerang Windows account. It is acceptable to grant other registered SQL logins ownership to Boomerang tables or read/write access, however one should exercise caution to prevent risk of exposing sensitive data to un-trusted applications and/or parties.
If a master table lacks spare column to store required data you may opt to create additional tables to facilitate such storage. The only exception to the rule is EVENT_MASTER table, to which it is acceptable to add columns and indexes.
List of Tables
|CODE_FILE||This table is intended to be used to gather all types of codes that might help you simplify and standardize frequent used information i.e. instead of typing information you can simply select appropriate code from this table.|
|CONTENT_PARAMETER||This table stores the report parameter and value in the event that the content are supplied by a SQL Reporting Service report and that the report requires parameter(s).|
|EVENT_CONTENT||This table is used to specify what type of content to be used. Depending on the service you are using different fields apply.|
|EVENT_LOG||This table is updated by the Boomerang and contains a log of all events generated by any of the services.|
|EVENT_MASTER||As the name indicates this is the master table which most tables are depended on. The primary purpose of event_master is to control the status of a job. The secondary role of the table is to provide user defined classification, grouping, labeling etc. This is made possible with a number of generic fields in different types.|
|EVENT_STATUS||This table is updated by Boomerang and contains current status of all events.|
|IN_EMAIL||This table contains all e-mails sent to Boomerang. If the original e-mail was sent by Boomerang and tracking is turned on (follow link for more information) the jKey will populated so that you can easily retrieve the message thread.|
|IN_EMAIL_CONTENT||This table contains all e-mail attachments sent to Boomerang.|
|IN_EMAIL_HEADER||Table contains e-mail header information from received e-mails.|
|IN_EMAIL_RECIPIENT||Table contains all recipients for each e-mail received by Boomerang.|
|IN_TWIT||Table contains all Twitter status updates sent to Boomerang.|
|IN_TWIT_HEADER||Table conatins Twitter header information from Twitter status updates sent to Boomerang.|
|OUT_EMAIL||This table is the main table for the e-mail out service. Records inserted into this table will be sent out. The table contains information regarding to the sender of the e-mail and message subject and body.|
|OUT_EMAIL_RECIPIENT||This table contains destination e-mail address/name pairs to compliment entries in OUT_EMAIL.|
|OUT_FAX||This table is the main table for the fax out service. Records inserted into this table will be faxed out. The table contains information regarding to the sender and receiver of the fax and fax number to use.|
|OUT_FILE||This table is the main table for the file out service. Records inserted into this table will be saved to a network share.|
|OUT_PRINT||This table is the main table for the file out service. Records inserted into this table will be printed to a network printer.|
|OUT_TWIT||This table is the main table for the Twitter out service. Records inserted into this table will be posted to the Twitter account associated with Boomerang.|
|SYSTEM_VARS||This table contains Boomerang Services runtime parameters. For more information on system parameters click here.|