TAP

Here are small effective hints on how you can improve the processing of your ADQL queries:

Include constraint(s) on a position with the ADQL geometries (e.g. CONTAINS, CIRCLE, POINT)
Include constraint(s) on Healpix indices at level 6, 7, 8 or 9 with the function ivo_healpix_index(...) (see examples on the side)
Avoid SELECT * ; 152 columns for DR3 is really a lot of data to fetch from the database... it takes space and time. You can check the columns for each table below.
Try to use indexed columns as much as possible and put a constraint on these alone (i.e. not inside a complex math. expression)
In the case of Gaia DR3, use the gaiadr3.gaia_source_lite table, as it contains less columns being a lightweight version of gaiadr3.gaia_source

Query

For data obtained on HTML, JSON or TABLEDATA-serialised VOTable format you can view it on a pop-up window. This will allow you to peek into the data. Please be aware that when plenty of rows/columns are queries this might be slow and/or hard to navigate as it will render on the client side. In any case, downloading the data is suggested.

You can quickly paste the name of a column or a table into the ADQL query text just by clicking on its name on the lists below (please be aware of the spacing).

Available tables & columns

Javascript is needed to see the list of columns here. But you can see all tables and columns provided by this TAP service on this page: /tap/tables.

Query

Examples

Available tables & columns