2011

4 When you finish inspecting the schema, click Cancel to close the Schema
Editor.
Editing a Schema
You can edit a schema (page 2073), feature class (page 2063), or property (page 2071)
if the
FDO provider (page 2063) supports updateable schemas (for example,
Microsoft SQL Server, SQL Server Spatial, MySQL, Oracle, and SDF all support
updateable schemas). For more information about data types and supported
functionality, see
Schema Editor (page 1739).
If you open a non-updateable schema in the Schema Editor you can
view
(page 608) its settings, but you cannot change them.
You cannot edit or delete any schema, feature class, or property if there are
existing features that use it.
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 data stores, see
Migrating DWG Data to GIS
(page 628).
Z and M Dimensions
The FDO Provider for SQL Server Spatial does not support Z and M dimensions,
due to limitations of their support by SQL Server 2008. When you define new
geometry properties for feature classes in the AutoCAD Map 3D Schema Editor,
the options to include Z and M will not be available.
Naming Restrictions
You can use the Schema Editor to import a feature schema collection from an
XML file. When importing, you can modify these schemas to conform to the
restrictions of the current provider connection.
For example, if you are connected to an Oracle data store, feature class names
may be limited to 22 characters. If you import a feature schema collection
that includes feature class names that are longer, you will need to rename
those feature classes during import to meet the restrictions of the Oracle
connection.
610 | Chapter 4 Managing Data