I recently ran into the following problem: Problem: Data type in a feature class converts to double when exported from a non-spatial database to an ArcSDE geodatab… I had assumed the data copied to the SDE geodatabase as it was defined in the file geodatabase. We discovered later that the copy converted the float fields to doubles. I would like a way to specify the precision and scale when copying a float to an sde geodatabase. If this isn't possible, at a minimum, there should be a warning that the data is not copying as defined.
... View more