Tableau Hyper Writer Parameters
Default Schema
Hyper files may contain multiple schemas. The writer will use the Default Schema parameter value as the schema for tables if not specified in the feature type name.
The default schema for Hyper tables is public, which will be used even if this parameter is empty.
Overwrite Existing Database
When this option is checked, the Hyper writer will delete the destination .hyper file, if it already exists.
The default setting is unchecked (set to No).
Advanced
Delete Hyper Logfile
By default, this option is set to Yes, which means that the Hyper log file created by Tableau (hyperd.log) will be deleted on completion of the workspace.
Select No to keep the additional log file.
Bulk Insert
Determines whether the Hyper writer will attempt to buffer insert records and add them in bulk. By default, this option is set to Yes, which can improve performance in cases where many features are being inserted, but will not guarantee the order of operations matches incoming feature order when INSERT features are mixed with UPDATE and DELETE features, or between feature types.
Select No if the workflow is sensitive to feature ordering.
The number of features that FME places in each transaction before a transaction is committed to the database.
If the parameter is set to 0, then the entire write operation occurs in a single transaction.
Default: 1000
This parameter allows for the execution of SQL statements before writing to a table. For example, it may be necessary to clean up a table before attempting to write to it. The statements will be executed only when the first feature arrives at the writer.
For detailed information about SQL functions, click the corresponding menu item in the .
Available menu options depend on the format.
Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.
For example:
FME_SQL_DELIMITER ; DELETE FROM instructors ; DELETE FROM people WHERE LastName='Doe' AND FirstName='John'
Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.
Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.
This parameter allows for the execution of SQL statements after a set of tables has been written. For example, it may be necessary to clean up a temporary view after creating it.
For detailed information about SQL functions, click the corresponding menu item in the .
Available menu options depend on the format.
Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.
For example:
FME_SQL_DELIMITER ; DELETE FROM instructors ; DELETE FROM people WHERE LastName='Doe' AND FirstName='John'
Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.
Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.

