The SDE writer module stores FME features in an SDE database. The SDE writer module provides the following capabilities.
- Transaction Support: The SDE writer provides transaction support that eases the data loading process. Occasionally, a data load operation terminates prematurely due to data difficulties. The transaction support provides a mechanism for reloading corrected data without data loss or duplication.
- Table Creation: The SDE writer module uses the information within the FME mapping file/workspace to automatically create SDE tables as needed. If the tables will be storing geometry, then feature classes, raster maps, or raster catalogs can be created.
- Table Validation: When data is loaded into an existing table, the SDE writer module performs validation operations between the layer or raster column definition in the mapping file and that within the SDE. All discrepancies found are logged. All critical discrepancies result in the data load operation being halted.
- Versioning Support: The SDE writer provides versioning support that allows users to modify data to existing tables without affecting what other viewers see in their own versions of the SDE database. Note: Not currently supported for raster tables.
- Geometry Demotion: Demotes incorrect polygons to linear shapes if there are data problems, but the data is to be loaded “as is” into the SDE.
- Non-Homogeneous Aggregate Loading: Provides the ability to load non-homogeneous aggregates into SDE layers by splitting the aggregates into several homogeneous aggregates.
- Non-spatial Index Creation: The SDE writer module can also define non-spatial indices. Indices are specified to increase the performance of searches having a non-spatial component.
- Update Capability: The SDE writer module enables features to be updated in SDE through the use of specified keys and the UPDATE mode of operation. If area replacement of features is desired, this can also be accomplished by combining the capabilities of the SDE writer with the SDE30QueryFactory. Note: Updating is the only way to add data to a raster map table, and is referred to as mosaicking.
- Rejected Features’ Pipeline: Features initially rejected by SDE can be sent through an FME Pipeline where changes can be made to the feature so that it can be accepted by SDE on its second attempt.
- Geodatabase Writing Support: Features can be written to an existing feature class located on an Enterprise Geodatabase.