Exporting Exposure Views To a Database
Exposure to Database enables you to export one or more exposure views to a single new or existing CEDE 2.0 database for further analysis or review. Since exposure views can contain one or more exposure sets, this function enables you to merge the exposure sets in an exposure view into a single exposure set. For example, Exposure View A contains three exposure sets (1, 2, and 3) on database X. When you export Exposure View A to database Y, the copy of Exposure View A will contain a single exposure set, which contains all three exposure sets that are in Exposure View A.
Contract IDs must be unique in an exposure set. Therefore, if there are duplicate contracts in the exposure sets that you are exporting, the system appends a suffix to the contract ID. For example, "ContractID129383" becomes "ContractID129383_2". Changing the contract ID does not affect the contract's layers, sublimits, reinsurance, or locations.
The exported exposure views maintain the same structure as the source exposure views except that they reside on a single database. In addition, since Export to Database copies the exposure sets within the selected exposure views, any filters that were applied to the selected exposure views are reflected in the copied exposure sets.
Procedure
To export exposure views to a database: