Timeline for Change feature class from ESRI native geometry to SQL Server geography
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 26, 2016 at 0:11 | comment | added | Vince | Migrating a layer is likely to fragment it, impairing performance. Copying to a new table is actually superior to most migration options. | |
| Apr 25, 2016 at 20:33 | comment | added | geo_coder | also discovered a potential reason why the migrate storage process runs and succeeds but doesn't do anything - According to ESRI documentation: If the editable feature layer contains m-values, you can't edit the geometry for existing features. To edit geometry for existing features in the layer, the layer owner must move the data with m-values to a separate layer (which can be in the same service). | |
| Apr 25, 2016 at 18:50 | history | answered | geo_coder | CC BY-SA 3.0 |