2011

use schema mappings to rename schema elements that you copy, to be sure
they meet the naming rules of the destination data store.
You can also pass in a set of schema capabilities to the target data store, so
the cloned schemas conform to the capabilities of that data store.
When you copy geodetic polygons with clockwise rings to SQL Server Spatial,
check Unmatched Data Or Geometric Type Errors as an error type to ignore.
For geography, SQL Server Spatial considers the inside of a polygon to be to
the left of the outer boundary. If a polygon with a clockwise boundary is
inserted, the polygon actually covers the rest of the world, excluding what
appears to be inside the polygon from an onscreen perspective. If you ignore
unmatched geometry type errors when using Bulk Copy, the geometry and
orientation are adjusted when the target is SQL Server Spatial. If you do not
check this option and you copy a polygon with the wrong orientation to SQL
Server Spatial, that object will fail to copy.
Also, SQL Server Spatial does not currently support such polygons that are
bigger than one hemisphere.
Other Ways to Migrate Data
If you are moving data from DWG format to any other format, you cannot
use Bulk Copy. Instead, see
Migrating DWG Data to GIS (page 628).
If you are moving geospatial data into SDF format, it may be easier to save or
export its Display Manager layer to SDF, without going through Bulk Copy.
See
Saving or Exporting a Display Manager Layer (page 1469).
Things to Remember
When using Bulk Copy, keep in mind the following points :
■ The copied schema is created if it does not exist in the destination feature
source.
■ The names of schemas, feature classes (page 2063), and properties in the
source feature source do not need to match the names in the destination
feature source.
■ You can save or load an XML mapping file to set up the mapping between
the source and destination feature sources.
■ You can copy geometry with no transformation of the coordinates.
■ You must make sure that the data you are moving are inside the extents
of the destination data store. (When you
create a data store (page 586), you
Migrating GIS Data (Bulk Copy) | 619