2011

The new data store is created when you click Apply in the Schema Editor.
You are connected to it automatically.
Creating FDO-Enabled SQL Server Spatial Data Stores
You can create a SQL Server data store in native SQL Server format (page 559)
and you can create
an extended SQL Server Spatial data store (page 561) with
FDO metadata.
NOTE This functionality affects geospatial feature data only. For information about
linking records in an external database to objects in a drawing, see
Overview of
Linking Database Records to Objects
(page 522). For information about moving
data between DWG and geospatial formats, see
Migrating DWG Data to GIS (page
628).
FDO-enabled Data Stores
You specify whether the new data store will be FDO-enabled or not by selecting
Use FDO Enabled Schema when you create a data store.
FDO-enabled data stores include additional FDO metadata, but otherwise use
native SQL Server schema capabilities.
■ Such metadata provides a mechanism for ensuring that class and property
names are maintained when you use Bulk Copy to move the data to a
different format and back again. For SQL Server, the cases where class and
property names are not maintained are rare, since SQL Server can handle
names with any Unicode characters. The names cannot be longer than
128 characters, which is not usually a problem.
■ FDO data stores maintain class inheritance, while non-FDO data stores do
not. ApplySchema for non_FDO data stores maintains the inherited
properties for sub-classes but not the relationships between classes and
sub-classes.
■ Object and object collection properties are supported only with FDO
metadata.
■ Revision number support for optimistic concurrency is included only with
FDO metadata.
■ If you select Use FDO Enabled Schema when you create a data store, some
columns or tables may be renamed in the SQL Server database to avoid
590 | Chapter 4 Managing Data