MSSQL Spatial Writer: User Attributes

This type is used to represent 64-bit signed integers.

This type is used to represent fixed length binary data up to a length of 8000 bytes.

This type is used to represent an integer with a value of 1 or 0.

This type is used to represent fixed length character data up to a length of 8000 bytes. The number of characters that can be stored depends on the code page of the server.

This type is used to represent date data from January 1, 0001 to December 31, 9999. FME supports the years 1000 to 9999.

For writers, as long as the input value is a valid date/time, and it contains a date component, the date component will be written; otherwise, null is written.

See Standard FME Date/Time Format.

This type is used to represent date and time data from January 1, 1753 to December 31, 9999 with an accuracy that is rounded to the nearest 0, 3, or 7 milliseconds.

When Bulk Insert = Yes, writers support writing fractional seconds; otherwise, they do not.

For writers, as long as the input value is a valid date/time, and it contains a date component, a datetime value will be written, with midnight appended if the time component is missing. If the input is not a valid date/time, null is written.

If input date/time has greater precision than supported by the database, the writer rounds the input fractional seconds to within the supported precision.

See Standard FME Date/Time Format.

This type is used to represent date and time data from January 1, 0001 to December 31, 9999 with an accuracy of 100 nanoseconds (7 fractional digits). FME supports the years 1000 to 9999.

For writers, as long as the input value is a valid date/time, and it contains a date component, a datetime value will be written, with midnight appended if the time component is missing. If the input is not a valid date/time, null is written.

If input date/time has greater precision than supported by the database, the writer rounds the input fractional seconds to within the supported precision.

See Standard FME Date/Time Format.

This type is used to represent 64-bit floating precision numbers.

This type is used to represent an auto-incrementing integer field.

If you try to write a value to it; the value will be ignored and the database will simply take the largest integer in the column, increment it and put that number into the field.

This type is used to represent variable length binary data up to a length of 2^31-1 bytes.

This type is used to represent 32-bit signed integers.

This type is used to represent monetary data values from -2^63 to 2^63-1. Attribute values are real numbers such as 55.2354.

This type is used to represent fixed length character data up to a length of 4000 Unicode UCS-2 characters.

This type is used to represent variable length character data up to a length of 2^30-1 Unicode UCS-2 characters.

This type is used to represent fixed precision and scale numeric data from -10^38+1 to 10^38+1.

This type is used to represent variable length character data up to a length of 4000 Unicode UCS-2 characters.

This type is used to represent 32-bit floating precision numbers.

This type is used to represent date and time data from January 1, 1900 to June 6, 2079 with an accuracy of one minute.

For writers, as long as the input value is a valid date/time, and it contains a date component, a datetime value will be written, with midnight appended if the time component is missing. If the input is not a valid date/time, null is written.

If input date/time has greater precision than supported by the database, the writer rounds the input fractional seconds to within the supported precision.

See Standard FME Date/Time Format.

This type is used to represent 16-bit signed integers.

This type is used to represent monetary data values from -214748.3648 to 214748.3647. Attribute values are real numbers such as 55.2354.

This type is used to represent variable length character data up to a length of 2^31-1 bytes. The number of characters that can be stored depends on the code page of the server.

This type is used to represent time data with an accuracy of 100 nanoseconds (7 fractional digits).

For writers, as long as the input value is a valid date/time, the time component will be written. If the time component is missing, midnight (00:00:00) will be written. If the input is not a valid date/time, null is written.

If input date/time has greater precision than supported by the database, the writer rounds the input fractional seconds to within the supported precision.

See Standard FME Date/Time Format.

This type is used to represent numbers between 0 and 255.

Uniqueidentifier is used to represent GUIDs. As such, it must be set up like a valid GUID. Example: {B85E62C3-DC56-40C0-852A-49F759AC68FB}

Note: The {} must be present for the GUID to be written successfully.

This type is used to represent variable length binary data up to a length of 8000 bytes.

This type is used to represent variable length character data up to a length of 8000 bytes. The number of characters that can be stored depends on the code page of the server.

This type is used to represent XML documents and fragments.