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."
That issue leads you right into these concerns too:
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?
Keep the following in mind when deciding whether to use mixed-release connections: