Difference: ADQLGeomOnSQLServer (2 vs. 3)

  META TOPICPARENT 
  name="DaveMorris"
- META TOPICPARENT
+  name="DaveMorris"
-<
<
+ADQL geometric functi"> SQLServer & ADQL geometric functions
->
>
+ADQL geometric functi"> SQLServer & ADQL geometric functions
 Page for discussions about supporting the ADQL geometric functions in SQLServer.

 Current deployments 

 ROE 

The main science archives at ROE are hosted on a set of SQLServer databases.

Our current TAP services do not support the ADQL geometric functions.
-<
<
->
>
+ MAST
->
>
+Many MAST holdings, including the Registry and a growing set of multimission data in ObsCore, are hosted on a set of SQLServer databases.

Nearly completed TAP services are not currently published. Release is held up on a library for parsing ADQL to SQL Server-flavoured queries. It needs to handle differences in left/etc join syntax (some canned TOMCAT RegTAP queries don't work), the ivo_string_agg function (for RegTap only), and ADQL geometric functions.

Brian McLean has written a series of database procedures mapping the HTM-based regional queries used by existing MAST services to the SQL Server's built-in geometric functions. Testing suggests similar performance to the old HTM-based system.