I recently migrated my SDE geodatabase from SQL 2005 to SQL 2008. The SHAPE.area and SHAPE.len fields automatically changed to SHAPE.STArea() and SHAPE.STLencth(). I believe this is because of the new geometry data types available in SQL 2008 and later. A simple change in the field names doesn't really present a problem until I export feature classes to a file geodatabase.
When feature classes are exported the SHAPE.STArea() and Length fields are retained, and additional Shape_Area and Shape_Length fields are created. Now there are redundant area and length fields and none can be deleted. Also, the area fields are different by as much as several square feet in some cases.
How can I avoid or work around these additional fields. I replicate the entire SDE database as a file geodatabase, so one by one featureclass manipulation isn't ideal.
Thanks,
Justin
When feature classes are exported the SHAPE.STArea() and Length fields are retained, and additional Shape_Area and Shape_Length fields are created. Now there are redundant area and length fields and none can be deleted. Also, the area fields are different by as much as several square feet in some cases.
How can I avoid or work around these additional fields. I replicate the entire SDE database as a file geodatabase, so one by one featureclass manipulation isn't ideal.
Thanks,
Justin