Use SQL Server Spatial
to connect to Microsoft® SQL Server™ Spatial data stores,
and to read, create, and edit schemas for SQL Server Spatial data
AutoCAD Map 3D supports SQL
Server authentication and Windows authentication for SQL Server
Spatial data stores. The FDO User
is mapped to the SQL Server login. Grant access to the databases
whose data you want to use.
SQL Server Spatial includes
two spatial data types: geometry and geography. Geography is used
for geodetic data, such as latitude/longitude data. Geometry is
meant for all other spatial data. The two spatial data types support
have a Geometry or Geography column, depending on the coordinate
system of the associated spatial context for the property. If the coordinate
system is geodetic, it has a Geography column. Otherwise, it has a
Geometry column. A coordinate system is Geodetic if its “well known
text” (WKT) starts with GEOGCS.
What SQL Server Spatial
A SQL Server schema can
support the following:
- Multiple schemas
- Object properties (with limitations)
- Association properties (with limitations)
- Schema overrides
- Auto ID generation
- Default values
- Inclusive value range constraints
- Exclusive value range constraints
- Value constraints list
- Null value constraints
- Unique value constraints
- Composite unique value constraints
- Spatial contexts
- The following geometry types:
- Polygons: polygon, multi-polygon
- Points: point, multi-point
- Line strings: line string, multi-line
Restrictions of SQL Server
When you create a SQL
Server schema, the following restrictions apply:
- A feature class must
define or inherit at least one identity property.
- M and Z dimensions are not supported.
- Identity properties cannot be nullable.
- Read-only identity properties must be
- A feature class can have multiple geometric
properties. Although it is not mandatory, having a main geometry
as an attribute of the feature class can help you to identify which
geometry property to use as the default for queries and rendering.
- The maximum length of a string is 4000
- For decimal properties, the precision
must be between 1 and 38, inclusive, and the scale must be between
0 and 38, inclusive.
- Long transactions and persistent locking
are not supported.