GeoMedia SQL Server Warehouse Writer Feature Type Parameters

This parameter lets the user specify how features will be written into the destination table. Supported feature operations are:

• Insert: Append rows onto the destination table using attributes on features.
• Update: Update existing table columns using attributes on features. A selection method must be specified in the Row Selection group.
• Delete: Delete existing table rows. A selection method must be specified in the Row Selection group.
• fme_db_operation: The feature operation will be determined by the attribute fme_db_operation on each input feature. A selection method must be specified in the Row Selection group. The value of fme_db_operation will be processed as follows:
  • If the value is null, empty, or missing, it will be treated as Insert.
  • The value will next be matched to Insert, Update, and Delete, case insensitively.
  • If there is no match, the feature will be rejected.
  • If there is a match, the matched feature operation will be performed on the feature.

Tip: The fme_db_operation attribute will cause feature rejection when Feature Operation is set to Insert, Update, or Delete.

More information on Feature Operations.

Controls how the feature type handles destination tables or lists:

• Use Existing – Write to an existing table or list. If the destination table/list does not exist, the translation will fail.
• Create If Needed – Create the destination table/list if it does not exist.
• Drop and Create – (This option is not available for all formats.) Drop the destination table/list if it exists, and then create it. The writer will drop and re-create the table before writing any features to it. Tables will be overwritten when the first input feature is processed. If no features are sent to a feature type, then the corresponding table will not be overwritten.
• Truncate Existing – (This option is not available for all formats.) If the destination table/list does not exist, the translation will fail. Otherwise, delete all rows from the existing table or list.

When updating features, users have a choice to update, or skip, their spatial column(s). Possible options are:

• Yes: The spatial column(s) specified by the user will be updated. IFMENulls will be written as null values and replace existing spatial values.
• No: No spatial columns will be updated.

When inserting into a table, Row Selection is ignored. When updating and deleting from a table (if applicable, based on a format's available Feature Operation options), a condition needs to be specified for selecting which rows to operate on. This parameter group offers two methods to construct the selection condition:

Match Columns

The columns specified in the corresponding column picker dialog will be used for matching destination rows. All matching rows will be selected for update or delete. If any feature attributes corresponding to the specified match columns contain null or missing values, the feature will be rejected.

WHERE Clause

This parameter opens a WHERE Clause Builder. You can also type a WHERE clause inline, without launching the Builder. It is optional to start the clause with the word WHERE.

The WHERE Clause Builder makes it easy for users to reference feature attribute values, destination table columns, and invoke FME functions. The WHERE clause is first evaluated as an FME expression, before being passed onto the destination database.

If the WHERE clause is incorrect or if its evaluation results in failure, the translation will fail. Otherwise, if the WHERE clause passes FME evaluation but it is SQL invalid, the feature will be rejected or the translation will fail.

For advanced users, conditional FME expressions created through the Conditional Value editor can be used to create WHERE clauses.

Tip: You can set the WHERE Clause to an attribute. This supports workspace migration and existing workflows involving fme_where. (Direct support for fme_where has been deprecated.) To advanced users who are accustomed to using fme_where, if Feature Operation is set to Update, Delete, or fme_db_operation, an fme_where attribute that conflicts with Match Columns or WHERE Clause will result in feature rejection.

If the User Attributes tab does not contain a primary index column, and Table Handling causes table creation, a primary index column is created with this name.

This parameter controls the creation of a clustered index, which only occurs on table creation. These options are available:

• None: all indexes are created as non-clustered.
• Primary: the primary index column is created as a clustered index.
• Extents: a clustered index on the four extent columns ( <geom>_XLO, <geom>_YLO, <geom>_XHI and <geom>_YHI) will be created, and the primary key column will have non-clustered index.

If a table is being created, this field allows the user to specify the name of the geometry column.

If the table already exists, and it has multiple geometry columns, then the geometry is written to the column specified in this field.