How to migrate existing SDEBINARY/SDELOB data to a native spatial type

[Anonymous User]

We are currenty using sql 2012 but our data is stored with SDEBINARY. What will it take to migrate to a SQL native spatial type?  Also we have assets in the UK as well as Canada and the U.S. should we go to Geography and support data with different projections or use Geometry and use WGS84 for all data submissions? I am leaning towards migrating to GEOMETRY and force all submissions to be in WGS84.

from ESRI "

"[Updated June 15, 2015] While we are not announcing the deprecation of the Esri binary storage geometry types (SDEBINARY with Oracle and SQL Server and SDELOB with Oracle only), this is to serve notice that new features supported in SQL spatial types may not be supported in the binary storage geometry types. Esri recommends that customers consider migrating existing SDEBINARY/SDELOB data to a native spatial type to leverage new functionality."

[JakeSkinner]

Hi Scott,

The migration is easy, you will just have to use the Migrate Storage tool.  As for Geometry vs Geography, I found a short read about the difference between 2 here.

[BillFox]

Hello Scott,

That issue leads you right into these concerns too:

• Client compatibility with previous desktops/server connections.
• New method of storing the geometry in newest level of the geodatabase vs separate tables.
• Data born in Arc/Info Coverage with spatial column named LAYER vs SHAPE.
• Area & Length morphing between projections (horizontal & vertical).
• Maintaining true-curves
• Enabling functionality for a feature class that only ArcGIS Pro can connect to.

-Bill

[Anonymous User]

Thank you Bill. Can you elaborate on the comment "Enabling functionality for a feature class that only ArcGIS Pro can connect to". If we go to SQL spatial data type :GEOMETRY, only GIS Pro can connect?

[BillFox]

Compatibility between ArcGIS clients and geodatabases in SQL Server—Help | ArcGIS Desktop 

Rules for mixed-release connections

Keep the following in mind when deciding whether to use mixed-release connections:

• If your organization uses a mix of ArcGIS 10.5, ArcGIS Pro 1.4, and older ArcGIS clients with a 10.5 or newer release geodatabase, the older clients will not be able to open datasets created with ArcGIS 10.5, ArcGIS Pro 1.4, or newer clients. If you need to keep the older ArcGIS clients, be sure all new datasets are created or loaded using the older ArcGIS client.