kreuzrsk

Appends When Geometry Storage Type Differs?

Discussion created by kreuzrsk on Jun 20, 2014
Latest reply on Sep 3, 2014 by kreuzrsk
When I upgraded from 10.0 to 10.1 the default geometry storage changed from SDEBinary to Geometry which initially I didn't notice.  So the original feature classes all use SDEBinary and everything added since the migration is stored using the Geometry (SQL spatial).  But now my exising workflow is broken. The Append command doesn't work if the target and source featureclasses use different geometries.  Why does this fail when I can do an Append between an feature class in a FGDB and an SDE database?


Executing: Append 'Database Connections\xxxxxxxxxxxxx\GeoWeb.DBO.Road_wm' "Database Connections\vSQL3 GeoWeb.sde\GeoWeb.DBO.Road" TEST # #
Start Time: Fri Jun 20 13:41:59 2014
ERROR 000466: Database Connections\xxxxxxxxxxxx\GeoWeb.DBO.Road_wm does not match the schema of target
Database Connections\vSQL3 GeoWeb.sde\GeoWeb.DBO.Road
Failed to execute (Append).
Failed at Fri Jun 20 13:41:59 2014 (Elapsed Time: 0.00 seconds)


Env: SQL 2012 / SDE 10.1 / Desktop 10.1

Outcomes