|API Reference||Autodesk FDO Provider for SQL Server|
The Feature Data Objects (FDO) API provides access to data in a data store. A provider is a specific implementation of the FDO API that provides access to data in a particular data store. The FDO Provider for SQL Server provides FDO with access to a Microsoft SQL Server-based data store.
SQL Server provides comprehensive data support, along with spatial indexing, optimistic concurrency, and read-committed transaction isolation. It uses a revision number for optimistic concurrency.
SQL Server authentication is supported for SQL Server data stores. The FDO User is mapped to the SQL Server login. Grant access to the databases whose data you want to use.
A SQL Server schema can support the following:
- Multiple schemas
- Object properties
- Association properties
- Schema overrrides
- Auto ID generation
- Inclusive value range constraints
- Exclusive value range constraints
- Value constraints list
- Null value constraints
- Unique value constraints
- Composite unique value constraints
- Spatial contexts
- These geometry types: point, line string, polygon, multi-point, multi-line string, multi-polygon, curve string, curve polygon, multi-curve string, multi-curve polygon, linear ring, line string segment, circular arc segment, and ring.
When you create a SQL Server schema, the following restrictions apply:
- A feature class must define or inherit at least one identity property.
- You cannot specify default values for data properties.
- Identity properties cannot be nullable.
- Read-only identity properties must be autogenerated.
- A feature class can have multiple geometric properties; main geometry is not mandatory, but this attribute of the feature class indicates which geometry property to use as the default for queries and rendering. HasMeasure and HasElevation are supported.
- The maximum length of a string is 8000 characters.
For decimal properties, precision must be between 1 and 38 inclusive and scale must be between 0 and 38 inclusive.
For more information, see The Essential FDO (FET_TheEssentialFDO.pdf) and the FDO Developer's Guide (FDG_FDODevGuide.pdf).