I'm having a weird error when I attempt to export a Query layer to a local file geodatabase.
I have a few different query layers that are directly tied to a SQL database. The query layers are displaying all of the fields and the number of records correctly, approximately 9000 records.
I can display X, Y coordinates from the query layer fine. When I do this the appropiate number of records display on the map and the fields are still ok. HOWEVER, when I attempt to export directly from the Query layer to a table in a local file geodatabase the final feature in the geodatabase gets reduced to approximately 77 records. The same occurs when I export the query layer XY events layer to a feature class in the local geodatabase.
I'm not sure if its something having to do with the geodatabase, the query layer, or the data itself is bad. Has anyone experienced an issue like this, where data record size was being reduced when imported into a file geodatabase?
I have a few different query layers that are directly tied to a SQL database. The query layers are displaying all of the fields and the number of records correctly, approximately 9000 records.
I can display X, Y coordinates from the query layer fine. When I do this the appropiate number of records display on the map and the fields are still ok. HOWEVER, when I attempt to export directly from the Query layer to a table in a local file geodatabase the final feature in the geodatabase gets reduced to approximately 77 records. The same occurs when I export the query layer XY events layer to a feature class in the local geodatabase.
I'm not sure if its something having to do with the geodatabase, the query layer, or the data itself is bad. Has anyone experienced an issue like this, where data record size was being reduced when imported into a file geodatabase?