New answers tagged


A couple of things that have caught you out here. In the SQL Server version using the Point, the order of the coordinate is Lat Lon, eg Y X. The OGC Point construct is X Y or Lon Lat. The next is that the PostGIS query you've posted actually returns 8.20039023523232e-005 which while appearing similar to the SQL Server result, is quite a lot smaller. The ...


OK, then this is the query, SQL Server 2012+ . I'll use test data instead of your query and omit all customer, order details but orderid. The query also doesn't use spatial features which doesn't help much here as we use no geography but plain geometry distance. with points as( select orderid, id, Coord_X, Coord_Y, rn = ROW_NUMBER() OVER(PARTITION BY ...


Upgrade should not fail (For this reason anyway). As stated in the link you provided, this is an application issue and only if it is directly accessing the Microsoft.SqlServer.Types.dll. The upgrade from 2008r2 to 2014 should work fine.


I managed to get this working I was assuming a 'Point' object was lat,lon but it's not as far as I can tell it's lon,lat. So in theory the problem was I had stored my initial 'Point' coordinate values the wrong way round in the table even though I thought the standard way was lat/lon


Providing the exact message from the Log\ERRORLOG file would be quite helpful since there are both multiple AppDomains and multiple reasons for AppDomains to get unloaded. Regarding the various AppDomains, there are AppDomains created for built-in CLR-based functionality, such as one that shows up in master when certain functions (e.g. FORMAT) and/or ...

Top 50 recent answers are included