2011

Bulk Copy uses the following rules when copying an auto-generated identifier
from the source
feature source (page 2063):
■ If the identifier exists in the destination schema (page 2073) and is not
auto-generated, the identifier is copied from the source feature source.
■ If the identifier exists in the destination schema and is auto-generated, the
identifier is generated by the destination provider.
■ If the identifier does not exist in the destination schema and the destination
schema does not support auto-generated identifiers, the schema is created
with a non-auto-generated identifier and the identifier is copied from the
source feature source.
■ If the identifier does not exist in the destination schema and the destination
schema supports auto-generated identifiers, the schema is created with an
auto-generated identifier and the identifier is generated by the destination
provider.
See also:
■
Migrating GIS Data (Bulk Copy) (page 617)
■ Reviewing the Bulk Copy Log Information (page 626)
■ Migrating DWG Data to GIS (page 628)
To copy data from one feature source to another (page 621)
NOTE This functionality affects geospatial feature data only. For information about
moving data between DWG and geospatial data stores, see
Migrating DWG Data
to GIS
(page 628).
Fixing Geometry Issues After a Bulk Copy
For foreign schemas, the Bulk Copy operation uses the first geometry it finds
to create the geometry in the target data store. If there are multiple spatial
indexes for the geometry properties in the original data store, the geometry
property in the resulting data store’s schema will be different from the order
in the original data store. As a result, the geometry in the new data store may
not match the geometry in the source.
You can fix this problem in the original data store or in the resulting data
store. If you fix the problem in the resulting data store, you modify the XML
file schema and import the modified version into the data store.
Fixing Geometry Issues After a Bulk Copy | 625