Microsoft SQL Server Spatial User Attributes

Readers: For information on the parameters in this dialog that are common to all readers, see:

Writers: For information on the parameters in this dialog that are common to all writers, see:

User attributes for this format are defined below.

Type

Description

bigint

Represents 64-bit signed integers.

binary

Represents fixed-length binary data up to a length of 8000 bytes.

bit

Represents an integer with a value of 1 or 0.

char

Represents fixed length character data up to a length of 8000 bytes.

Note   The number of characters that can be stored depends on the code page of the server.

date

Represents 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.

See Standard FME Date/Time Format.

datetime

Represents 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 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.

datetime2(width)

 

Represents 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 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.

(width) Specifies the number of digits for the fractional part of the seconds. The width can be an integer from 0 to 7.

datetimeoffset

Defines a date that is combined with a time of a day based on a 24-hour clock like datetime2, and adds time zone awareness based on UTC (Universal Time Coordinate or Greenwich Mean Time).

The maximum width for this attribute is 7.

float

Represents 64-bit floating precision numbers.

identity

Represents an auto-incrementing integer field.

Note  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 insert that number into the field.

image

Represents variable-length binary data up to a length of 2^31-1 bytes.

integer

Represents 32-bit signed integers.

money

Represents monetary data values from -2^63 to 2^63-1.

Attribute values are real numbers such as 55.2354.

nchar

Represents fixed-length character data up to a length of 4000 Unicode UCS-2 characters.

ntext

Represents variable-length character data up to a length of 2^30-1 Unicode UCS-2 characters.

numeric

Represents fixed precision and scale numeric data from -10^38+1 to 10^38+1.

nvarchar

Represents variable-length character data up to a length of 4000 Unicode UCS-2 characters.

nvarchar_max

Represents variable-length character data up to a length of 536,870,912 Unicode UCS-2 characters.

real

Represents 32-bit floating precision numbers.

smalldatetime

Represents 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 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.

smallint

Represents 16-bit signed integers.

smallmoney

Represents monetary data values from -214748.3648 to 214748.3647.

Attribute values are real numbers such as 55.2354.

text

Represents variable-length character data up to a length of 2^31-1 bytes.

Note  The number of characters that can be stored depends on the code page of the server.

time(width)

Represents 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 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.

(width) Specifies the number of digits for the fractional part of the seconds. This can be an integer from 0 to 7.

timestamp

Stores a unique number which is updated every time a row gets created or modified.

The timestamp value is based upon an internal clock and does not correspond to real time. Each table may have only one timestamp variable.

tinyint

Represents numbers between 0 and 255.

uniqueidentifier

Represents 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.

varbinary

Represents variable-length binary data up to a length of 8000 bytes.

varbinary_max

Represents variable-length binary data up to a length of 2 GB.

varchar

Represents variable-length character data up to a length of 8000 bytes.

Note  The number of characters that can be stored depends on the code page of the server.

varchar_max

Represents variable-width binary string to a maximum size of 2 GB.

xml

Represents XML documents and fragments.

Index

The type of index to create for the column.

If the table does not previously exist, then upon table creation, a database index of the specified type is created. The database index contains only one column.

Note  A given table can contain, at most, one clustered index.

The valid values for the column type are listed below:

  • Indexed – An index without constraints.
  • IndexedNotNull – An index with a non-nullable constraint.
  • Unique – An index with a unique constraint.
  • UniqueClustered – A clustered index with a unique constraint.
  • Clustered – A clustered index without constraints.
  • ClusteredNotNull – A clustered index with a non-nullable constraint.
  • NotNull – A non-nullable constraint.
  • PrimaryKey – A primary key with non-nullable and unique constraints.