Real SQL vs. Not Really SQL

Surprisingly, ArcGIS Pro does not have real SQL built-in. Instead, Pro has less than 5% of real SQL. Pro includes only a few bits of SQL-like syntax for very simple expressions. It's not SQL, but a painfully small slice of SQL.

Most SQL statements, clauses and other SQL syntax are not built into ArcGIS Pro. With 95% of SQL missing, including the most powerful parts, the 5% of syntax that ArcGIS Pro provides is not really "SQL" as real SQL users know it.

Real SQL syntax has around 90 or so statements and clauses. ArcGIS Pro "SQL expressions" are limited to only one statement, a limited SELECT statement, and only one clause, a limited WHERE clause. That's all there is in Pro.

ArcGIS Pro has no JOINs, no UPDATEs, no DISTINCT, no DROP, no ALTER, and none of the many other critically important capabilities that real life SQL users depend upon. Pro has no SQL for rasters. The sliver of SQL syntax in ArcGIS Pro is also read-only, a crushing limitation that gives up the intense power of SQL as a means of creating new tables and editing, updating, and transforming existing layers.

If you rely on the phenomenal power and convenience of SQL in databases, you want 100% of the power and convenience of SQL for your ArcGIS Pro desktop, not a 5% subset. Manifold^® Release 9 delivers 100% of SQL. Release 9 delivers real SQL and Esri ArcGIS^® Pro does not.

This page summarizes reports by Manifold users of why they consider SQL in Release 9 to be a superb SQL, especially for spatial work, and why ArcGIS Pro fails to provide a real SQL. See also the Spatial SQL page for info on SQL in Manifold, and the Real SQL page for comparisons to other GIS packages like Global Mapper, FME, MapInfo, and QGIS.

New !   Get Real SQL in ArcGIS Pro

New ! Esri users can now enjoy the world's best spatial SQL as an add-in to Esri's flagship desktop GIS package. Launch the full power of Manifold SQL from ArcGIS^® Pro.

SQL for ArcGIS Pro is a new add-in for Esri's ArcGIS Pro desktop GIS. The add-in provides spatial SQL for Esri file geodatabases in your ArcGIS Pro project in tight integration with ArcGIS Pro.

The add-in enhances ArcGIS Pro with the world's most powerful desktop spatial SQL engine, Manifold's Radian^® engine, to unleash the phenomenal power of SQL from your ArcGIS Pro desktop. Enjoy full-featured SQL, superior quality, and the amazing speed of parallel CPU and parallel GPU query execution, all supported with hundreds of SQL functions for every spatial need.

In Advanced mode the add-in runs spatial SQL with hundreds of file formats, databases, web servers, and other data sources outside of ArcGIS Pro. Ultrafast data storage in the add-in makes it easy to combine huge data from outside your ArcGIS Pro project with data inside the project.

When you read about the many advantages of real SQL in web pages like this, keep in mind that you can upgrade ArcGIS Pro to have real SQL as well by installing Manifold's SQL for ArcGIS Pro add-in.

Special introductory offer: Save $100 off the regular price of $245 - Only $145.   Visit the sql4arc.com website for complete information.

What's In the Package?

Manifold's desktop GIS includes within it an immensely powerful, fully parallel spatial DBMS, complete with an extensive, fully-articulated SQL engine. Launch Manifold and you always have the full power of SQL at your fingertips. In contrast, ArcGIS Pro has no DBMS inside and does not have a complete SQL engine. Instead, for real SQL Esri relies on Arc being a client to other software that provides a full SQL implementation.

With Manifold, if you open a shapefile you have full SQL. With Arc, if you open a shapefile you have an extremely limited ability to use some SQL expressions, but you don't get real SQL as experienced SQL users want. ArcGIS Pro doesn't even provide real SQL for file geodatabases, but Manifold does: if you want to enjoy the limitless power of real, full-featured SQL with Esri file geodatabases, run Manifold.

That may come as a surprise to Esri users who have heard Esri claims of real SQL capability when connected to Oracle or other DBMS packages.

Don't be led astray by comparisons that take credit for capabilities in third party software. Esri salespeople may cite the marvels of SQL when their product connects as a client to Oracle or SQL Server. But that is using Oracle's SQL, not Esri's SQL. With Esri, if you connect to Oracle, SQL Server, and PostgreSQL you need to know three different SQLs, because you'll be using three different SQLs provided by the three different database packages.

Run ArcGIS Pro without relying on Oracle, SQL Server, or some other DBMS, and then you'll be running native Arc SQL. What do you get? - A very small subset of SQL with woefully limited capabilities, basically just limited expressions, and you only get that for some data sources, such as file-based data sources like file geodatabases, shapefiles, and DBF tables. With other data sources, like GeoTIFF files, you get no SQL at all. It's that limited.

In contrast, with Manifold you always have full SQL for all data sources. Manifold provides genuine, full-fledged SQL, comparable to Oracle, SQL Server, MySQL, and PostgreSQL/PostGIS. Manifold exceeds even those fine SQL implementations in the hundreds of GIS-oriented spatial SQL functions Manifold provides. You don't need to install, learn, configure, load, and administer a huge, enterprise DBMS server to get superb spatial SQL in Manifold. You always have full-power SQL at your fingertips. Amazingly, the only way ArcGIS Pro users can use real SQL with file geodatabases is by getting Manifold. Manifold has real SQL for everything, and ArcGIS Pro does not, not even with Arc's "native" file geodatabase format.

With Manifold, it's all built-in with no need to buy, install, learn, or maintain anything extra. Manifold's full-power SQL is always there for you no matter what the data source, whether the data is local in your project or linked from an external data source. If you want to use the an external server's SQL, Manifold lets you do that too. You can even mix external SQL and Manifold's native SQL in the same query for a mix of server-side and client-side SQL capabilities.

Manifold Release 9 is only $145, fully paid. The world's most advanced spatial SQL is only $145. Amazing! That's the fully paid price for Manifold System Release 9. The fastest and most powerful GIS ever created now also has the world's lowest cost of ownership.

What do you need for a superb spatial SQL? There are ten points to consider:

Complete SQL Infrastructure

If you don't have all the JOINs you don't have an SQL: To have a real SQL you need a full roster of fully-implemented statements, clauses, aggregates, operators, and data types. Manifold has all that, providing a very extensive and fully articulated SQL, including statements like ALTER, DROP, UPDATE, and many more, including of course SELECT (with all the aggregates and other clauses like COLLECT, DISTINCT, SPLIT, INTO), all the various JOINs (JOIN, INNER JOIN, LEFT JOIN, RIGHT JOIN, FULL JOIN, LEFT OUTER JOIN, etc.), WHERE, GROUP BY, ORDER BY, UNION, EXCEPT, INTERSECT, and more. You not only get tremendously useful aggregates like COLLECT, you also get splitters (the reverse of aggregates) like SPLIT.

Manifold provides an extensive choice of data types, including a variety of geometry and vector (tuple) types, and operators, including tuple operators, CASE, CASE WHEN, CAST, CASTV, and much more. There are very long listings in the various SQL topics in the Manifold user manual.

Manifold not only has very broad implementation of SQL, it is also an exceptionally deep and thorough implementation. For example, Manifold fully supports Unicode with collations throughout Manifold SQL, something that not even IBM's highly-respected DB2 DBMS provides. There are endless details like spatial indices for vectors, rasters, and LiDAR point clouds, with indices automatically being surfaced in results tables, so if you generate a results table you can interactively edit through that results table, changing values in the cells to change the data within the database (either within Manifold's internal database, or any external database you might use).

Arc, in contrast, has an extremely limited, read-only SELECT with WHERE and that's about it.

Extensive Set of SQL Functions

You don't have a spatial SQL if you don't have an extensive roster of spatial SQL functions for various spatial tasks. A classic example of SQL functions playing a key role in spatial SQL are the spatial SQL functions provided for PostgreSQL by the PostGIS extension. Oracle and SQL Server both include spatial SQL functions as well.

Manifold has hundreds of SQL functions that service almost any need involving attributes, vectors, rasters, or combinations of attributes, vectors and rasters. For spatial SQL, Manifold has 136 geometry functions and counting. Manifold also provides a vast number of raster SQL functions.

In contrast, ArcGIS Pro appears to have no spatial SQL functions at all, not for vectors and not for rasters.

Considering only elementary SQL functions for manipulating non-spatial attribute data like text and numbers, ArcGIS Pro has very few SQL functions for routine tasks. For example, while Manifold has 77 SQL functions to manipulate strings (including functions for full use of regular expressions), ArcGIS Pro has only six, very simple, SQL functions for strings. With Arc, if you want to change upper case to lower case, or vice versa, Esri can help, as LOWER and UPPER are two of the six string functions. But if you want to search and replace substrings using regular expressions, you need Manifold.

Manifold also provides many spatial SQL functions that combine attribute, vector and raster data. These service raster to vector operations such as building contours, watersheds, and viewsheds, as well as vector to raster operations such as Kriging. There are also many utility functions that are essential for real world GIS automation in SQL, for example projection (coordinate system) services such as reprojecting vector or raster data, controlling the projection pipeline, manipulating projection definitions, registering raster or vector data using control points, and much more.

You can also define new SQL functions on the fly within a query in Manifold, a great way to organize queries for clarity and maintainability by modularizing repeated tasks within functions.

The combination of having a fully articulated SQL with an extensive set of spatial SQL functions provides spectacular SQL functionality not available in ArcGIS Pro, as illustrated as these SQL examples:

• Re-create Lines from a CSV Table of Points
• Extract Airport Runways from an OpenStreetMap PBF
• Unions using Topology Overlays
• Process RGB Images using Matrix Filters

Extensive Internal Automation

For an SQL implementation to be convenient in real life spatial tasks it has to do many housekeeping chores automatically and internally, like automatic conversion of coordinate systems. Manifold SQL automatically handles all coordinate systems, so you have greater freedom to mix geometries that use different coordinate systems in SQL expressions.

Manifold handles pathologies so you don't have to first eliminate overlapping polygons, bowties or other issues. Manifold automatically transforms whatever coordinate system you used into the closest SRID match when you upload into external DBMS packages or mix data from within Manifold and an external DBMS in the same query. There are hundreds of small details like that which are automated in Manifold's SQL engine.

Seamless Scripting

You can do scripting inline within a Manifold SQL query, and also launch Manifold SQL inline within a script. You can also call functions written in scripts, in any of the 10 languages Manifold supports, for example, in any .NET language, VBScript, Javascript, and more. All that works with any data source, so you can write a Manifold SQL query that connects to tables in your Oracle database and which, on the fly, calls an inline script to do custom work within the query.

Seamless Access to Enterprise DBMS

Manifold itself is a database with a full-power, native SQL engine so it's not restricted to just being a client. That makes it a much better partner for Enterprise DBMS installations. You can connect to an Oracle database, or to multiple external DBMSs, and run native Manifold SQL queries that utilize tables in all of them, as well as data stored in the Manifold project itself.

Or, you can write queries using whatever is the native SQL for the external DBMS to which a data source is connected. Or, you can write queries that are a mix of both external SQLs and Manifold SQL, all within the same query. That lets you write queries which can do something server-side in, say, Oracle, and then use that result within the query to do something in Manifold SQL that Oracle can't do, for example, a massively GPU parallel SQL expression.

ArcGIS Pro, in contrast, can only use whatever SQL the data source provides. That forces you to learn and to use a different SQL syntax for each different DBMS package that is running the enterprise geodatabase you use. If you connect to three different data sources, like Oracle, SQL Server, and PostgreSQL, you have to learn three different SQLs. When working with Esri file geodatabases, shapefiles or similar, you are limited to the small subset of SQL capabilities provided by ArcGIS Pro's partial SQL implementation.

With Manifold, you can connect to all those data sources at once and use the same full-power SQL from Manifold for all of them. Write one query that works with exactly the same syntax on all the different data sources, within Manifold or within any of the vast list of data sources and enterprise DBMS packages to which Manifold can connect. Or, if you like, use native SQL within the various data sources either standalone or mixed in with Manifold SQL.

For example, you can connect to Oracle, SQL Server, and PostgreSQL servers and in a single query write overall workflow in Manifold's native SQL, but then call three different subqueries each written in Oracle SQL, SQL Server SQL, and PostgreSQL SQL to do something server-side in each of the three servers, all within the same query overall.

Orthogonality

Everything in Manifold SQL works the same way regardless of whether the data source is the Manifold database (the project), a data source like Oracle or SQL Server, a linked file, or an SQL expression used within an argument box in a tool.

That's hugely important because it allows consistent writing of queries that always work, and a "learn once, use many times" model of learning how to work SQL. With Esri, in contrast, what you can do in SQL depends on what the data source is or where you are using the SQL expression.

Manifold SQL also works everywhere an expression works, which is in virtually all dialogs that take parameters. For example, when Transform pane templates provide a drop down box to enter or to choose an argument, you can choose Expression and write an SQL expression. Unlike ArcGIS Pro (which also allows limited SQL expressions in some tools), those expressions are not limited in Manifold but can be arbitrarily massive and complex if you want.

Practical Extensions

Practical use of spatial SQL is helped a lot by practical extensions. For example, in Manifold you can define new SQL functions on the fly within queries, which is a great way to write cleaner, more understandable, less error-prone, and more maintainable SQL. Functions you define can both take and return simple values like numbers or strings as well as tables. There are many other practical extensions, like the VALUE statement used to declare global values, which themselves can be expressions.

More than just a well-implemented SQL, Manifold's SQL engine includes multiple hardcore features specifically designed for spatial SQL in real life use with emphasis on performance and control: constraints, computed fields, spatial and non-spatial indexes, temporary tables and temporary databases, precisely controlled multi-threaded execution, offloading of advanced raster operations to GPGPU, read-only and transparent read-write caches, and much more.

Automatic CPU and GPU Parallelism

A superb spatial SQL is an automatically, fully CPU parallel and GPU parallel SQL. Manifold's seamless CPU and GPU parallelism is so advanced it is not available even in mainstream enterprise DBMS packages, which have not yet achieved GPU parallelism in SQL like Manifold.

CPU and GPU parallel SQL is built into Manifold - no need to buy or to install anything extra.

Manifold SQL parallelizes all query statements to use all CPU threads available: if you have 16 cores the query runs in 32 threads. Manifold also GPU parallelizes queries where that makes sense. Manifold SQL can execute on thousands of GPU cores in parallel for astonishing speed. In addition, most spatial functions include parallel versions with even better optimizations specific to the function.

ArcGIS Pro's Spatial Analyst extension, an expensive option, has a limited number of geoprocessing tools that are CPU parallelized, but ArcGIS Pro itself and "SQL" expressions within Arc are not parallel. For that matter, even Spatial Analyst's parallelization of geoprocessing tools is woefully partial, and is also hobbled by the bottleneck of a non-parallel ArcGIS Pro main application. See the Faster than Esri collection of videos to watch how full Manifold parallelization absolutely crushes partial Esri parallelization.

You get all that parallelization automatically in Manifold SQL: Write ordinary SQL and the Manifold query engine will optimize it and will parallelize it for execution, automatically utilizing CPU and GPU parallelism. If you have no GPU, Manifold will optimize for CPU parallelism. If you have a GPU, Manifold will optimize for a mix of CPU and GPU parallelism, on the fly adjusting for the best balance between the number and power of CPU and GPU cores that are available. If hardware is reconfigured, the same query automatically will be reoptimized during execution to take best advantage of the resources you have, to run at top performance.

GPU acceleration works everywhere in Manifold SQL where worthwhile work arises: in the SELECT list, in WHERE, in EXECUTE, ...everywhere. For example, if you add to a table a computed field that combines multiple tiles together, that computed field will use GPGPU. If you do some tile math in a FUNCTION, that FUNCTION will use GPGPU as well.

ArcGIS Pro SQL has no GPU parallelization at all. Manifold uses unlimited GPU parallelization everywhere, utilizing multiple GPUs even from different GPU generations, in hundreds of settings, with automatic GPU parallelization in SQL. GPU parallelization often runs 50 to 200 times faster than not having GPU parallelization: see the Parallel GPU page for examples and discussion on how massively parallel GPU computation in Manifold SQL works.

Extensive UI Support

A truly first-rate SQL doesn't force users to leverage SQL through the keyhole of an exclusively text interface: it also provides the power of SQL with numerous user interface (UI) enhancements. Manifold provides an extensive query builder with all statements and functions that makes it much easier to build SQL queries.

SQL is also totally integrated with Manifold point and click user interface tools, like the Transform pane and Select pane, the Join dialog, and similar. In panes and dialogs you can click the Edit Query button and Manifold will write a well-organized SQL query for you that accomplishes what has been set up in the dialog. That's a great way to learn SQL and also a great way to build queries for customization and repeated use.

Spatial Optimization

ArcGIS Pro is not a database: Arc itself is remarkably separate from, say, Esri's file geodatabase. Various other Esri tools and modules are also separate worlds. The resulting architecture is full of bottlenecks with no global optimization. Manifold, in contrast, itself is a database that is very tightly integrated with the rest of the system, with the entire architecture designed from bottom to top for parallelized spatial data work. Manifold's unified archiecture supports global optimizations that help eliminate bottlenecks for better performance, expecially with complex queries operating on larger data.

Manifold is also spatially optimized. Classic DBMS packages like Oracle originally were designed mainly for very many small transactions, typically with only a few thousand bytes per record, while spatial work usually involves very "fat" transactions, where an intersection between two complex objects like a big polygon and a very complex polyline (say, a contour in a large, complex terrain) could involve two records with over a gigabyte of data in each record.

Manifold's internal structure as a database was designed to handle such "fat" spatial transactions, and the Manifold SQL engine was designed to do highly complex global query optimizations on those on the fly. Special internal structures allow Manifold to achieve astonishingly fast performance for spatial work, often dramatically exceeding the speed of enterprise class DBMS packages for tasks like rendering large, complex vector layers.

Performance gains from parallel SQL optimization and spatial data optimization are so great that big, complex SQL queries in Manifold often will run faster than what can be hand coded using C++ or Python.

How Fast Is Manifold Parallel GPU?

If you are doing computations it's fast. Really fast. Gains are usually from 20 times faster to 100 times faster than running typical computations on CPU alone, even when using very inexpensive GPU cards. Running complex computations on faster cards, performance can be 100 to 200 times faster than using CPU alone. It's fairly common to do in a second or two what takes more than five minutes without Manifold.

If your time is worth more than minimum wage and you're doing anything that requires your machine to think at a higher level than your coffee pot timer, you'll often pay back the cost of a Manifold license the first time you use it for anything serious. It's that fast.

Bonus: Free Viewer with Full Spatial SQL

Manifold users can publish sophisticated projects that leverage the power of full, spatial SQL, complete with parallel CPU and parallel GPU speed that anybody can exploit for free, using the free Manifold Viewer. Viewer provides full Manifold SQL and full CPU and GPU parallelism. Viewer is read-only and does not support scripting, but publishing Manifold projects for use with free Viewer installations is a fantastic way to provide astonishing performance to anyone for free.

Links

Comments on ArcGIS Pro are based on Esri's ArcGIS Pro SQL Reference, which is recommended as a guide to SQL in ArcGIS Pro in Esri's Write a query in the query builder page. Suggestions for improvements and any corrections to this page by ArcGIS Pro users are welcome and encouraged.

---

New! Automate Complex Jobs with Manifold^® Commander

New ! Manifold^® Commander is a console application version of Manifold that provides the full range of Manifold query and scripting capabilities from a command line, making it easy to automate tasks.

Commander launches from a command line such as in a Windows Command Prompt window, or in a .bat batch file, or from a Windows PowerShell script, from within Windows Task Manager to automate tasks.  Commander can run either SQL queries or scripts from within a specified .map file, and Commander also can run scripts from a specified script file stored outside a Manifold project. Script in ten different languages!

• Your own Automated Factory - Commander provide an automated production line for accomplishing nearly any GIS, DBMS or ETL task. String together any of hundreds of functions using whatever logic you want in a sequence of SQL queries, or use scripts in any of ten different programming languages. Manifold features like the Transform pane will automatically write SQL that accomplishes what you've set up using point and click templates. It's like being able to tell a factory full of robots what you want them to do.
• Built into Universal and Server Editions - Manifold Release 9 Universal and Server licenses include Manifold Commander. Installing either Release 9 Universal or Release 9 Server automatically installs Manifold Commander. When you buy Release 9 Universal for $195 you automatically get Manifold Commander as well. There is no need to make any additional purchases to get Commander.
• Replace Costly and Slow ETL Tools - Commander is Manifold, so just like Manifold it runs fully parallel, with incredible parallel CPU and massively parallel GPU speed. Queries and scripts provide access to the full power of Manifold, enabling use of hundreds of Manifold functions and the full power of SQL and scripts to interact with data in databases or in any of hundreds of formats and data sources, to transform that data, do analyses, and save the transformed data or results or output to desired formats. Replace costly, non-parallel tools like FME at a fraction of the price.
• Schedule Tasks - Using Windows Task Scheduler you can launch tasks using Commander on a regular schedule, such as updating a CSV every night for serving to clients, updating databases, or converting files into different formats.

See the Manifold Commander user manual topic for details and illustrated, step by step examples.

---

Experience Manifold Power in a Free Tool

Manifold Viewer is the free, read-only version of Manifold Release 9. Although Viewer cannot write projects or save edited data back out to the original data sources, Viewer provides phenomenal capability to view and to analyze almost all possible different types of data in tables, vector geometry, raster data, drawings, maps and images from thousands of different sources. Viewer includes full SQL as well, with hundreds of spatial and other analytic functions.

Viewer can also create and write spatial indices for entire folders full of LiDAR files, save connections to favorite files and data sources, and even edit and save localization files to translate Manifold into new languages.

Manifold Viewer delivers a truly useful, fully CPU-parallel and GPU-parallel Manifold tool that gives you parallel power and endless Manifold capabilities at zero cost. No need to register, no adware, no requests for donations and no selling: use Viewer however you like, including commercial purposes. You can even redistribute Viewer, all for free.

Viewer is a great way to share the amazing projects you create in Manifold for free. Publish multi-hundred GB projects created in Manifold that anybody can pop open in 1/10th second for free using Viewer. Publish projects that include automatic connections to your organization's databases and worldwide webserved data, and include pre-built, sophisticated analytics and dynamic reporting that users can launch with a point and click. Track pandemics, help first responders fight wildfires, or just help your organization do a better job.

Viewer's small download (only 50 MB), instant launch, and clean display - free of convoluted ribbons and endless, confusing buttons - make it perfect for unskilled users. With Viewer a million people can share the dazzling analytics and insights you create with an inexpensive Manifold license, all at fully parallel speed with no need to pay for costly, cloud-based, web processing. Like Manifold, Viewer never crashes, no matter how big or complicated the job.

See Viewer in action Watch the Manifold Viewer Introduction YouTube video.

"Mfd 9 is becoming a really good tool for sharing data with non-GIS folks. Clean interface makes it easy to teach others simple tasks. Easy to transfer a project. Easy to install software. Free viewer." - Forum post

Get Manifold Viewer

---

Buy Now via the Online Store

Buy Manifold^® products on the Online Store. The store is open 24 hours / seven days a week / every day of the year. Orders are processed immediately with a serial number sent out by email in seconds. Enjoy the world's most advanced spatial tools today!

 

---

A Sample List

Tired of "spatial" SQL products that provide a handful of functions? That's not Manifold. Manifold has you covered for every possible need with a vast selection of SQL statements, operators and functions. Manifold's spatial experts with decades of experience in spatial engineering have provided everything that everyone from a novice to maximum expert will want, all neatly organized within the query builder with easy filtration to find just the right function for a task. Following is a sample list of some, but not all, of what you get in SQL with Manifold.

• ALTER
• ADD PROPERTY
• DROP PROPERTY
• ALTER TABLE
• ADD
• ADD CONSTRAINT
• ADD INDEX
• DROP
• DROP CONSTRAINT
• DROP INDEX
• RENAME
• RENAME CONSTRAINT
• RENAME INDEX
• CREATE
• PROPERTY
• CREATE DATASOURCE
• CREATE ROOT
• CREATE TABLE
• CONSTRAINT
• INDEX
• ASC/DESC
• COLLATE
• CASE/NOCASE
• ACCENT/NOACCENT
• SYMBOLS/NOSYMBOLS
• TILEREDUCE
• DELETE FROM
• DROP ROOT
• DROP TABLE
• EXECUTE WITH
• FUNCTION
• ENTRY
• ENTRYSCHEMA
• INSERT INTO
• PRAGMA
• PRAGMA PUSH
• PRAGMA POP
• RENAME TABLE
• SELECT
• DISTINCT
• COLLECT
• WHERE
• ORDER BY
• OFFSET
• FETCH
• INTO
• GROUP BY
• BATCH
• THREADS
• UNION EX /INTER
• UPDATE
• USE CHILD
• USE PARENT
• VALUES
• MOD
• DIV
• BITNOT
• BITAND
• BITOR
• BITXOR
• LIKE
• BETWEEN
• IN
• IS NULL
• NOT
• AND
• OR
• XOR
• CAST
• CASTV
• CASE WHEN
• CASE
• EXISTS
• Avg
• Corr
• Count
• Covar
• CovarPop
• First
• GeomMergeAreas
• GeomMergeLines
• GeomMergePoints
• GeomUnionAreas
• GeomUnionBoxes
• JoinAnd
• JoinBitAnd
• JoinBitOr
• JoinBitXor
• JoinOr
• JoinXor
• Last
• Max
• Median
• Min
• StDev
• StDevPop
• StringJoinTokens
• Sum
• Var
• VarPop
• Abs
• Acos
• Acosh
• Asin
• Asinh
• Atan
• Atan2
• Atanh
• BinaryWkbGeom
• Cbrt
• Ceil
• CeilDecs
• Chr
• Coalesce
• Collate
• Compare
• ComponentCoordSystem
• ComponentName
• ComponentPath
• ComponentProperty
• ComponentType
• CoordConvert
• CoordConvertPoint
• CoordConvertPoint3
• CoordConvertTile
• CoordConvertTrace
• CoordConverterIsIdentity
• CoordConverterIsScaleShift
• CoordConverterIsXYZ
• CoordConverterMake
• CoordConverterSteps
• CoordDatum
• CoordDatumDefault
• CoordDatumEpsg
• CoordDatumParameters
• CoordDatums
• CoordSystem
• CoordSystemDefault
• CoordSystemDefaultLatLon
• CoordSystemEpsg
• CoordSystemOverride
• CoordSystemParse
• CoordSystemParseEpsg
• CoordSystemParseOverrides
• CoordSystemParseSrid
• CoordSystemParseSridSubtype
• CoordSystems
• CoordSystemTypeParameters
• CoordSystemTypes
• CoordTransform
• CoordTransformEpsg
• CoordTransforms
• CoordTransformTypeParameters
• CoordTransformTypes
• CoordUnit
• CoordUnitByName
• CoordUnitDefault
• CoordUnitDefaultLatLon

• CoordUnitEpsg
• CoordUnits
• Cos
• Cosh
• DataLength
• DateTimeDay
• DateTimeHour
• DateTimeMillisecond
• DateTimeMinute
• DateTimeMonth
• DateTimeSecond
• DateTimeYear
• Erf
• Erfc
• Exp
• Exp10
• Exp2
• Expm1
• Floor
• FloorDecs
• Fract
• FractDecs
• GeocodeAddress
• GeocodeAddressMatches
• GeocodeAddressSupported
• GeocodeLocationMatches
• GeocodeLocationSupported
• GeomAdjacent
• GeomArea
• GeomBounds
• GeomBox
• GeomBranch
• GeomBranchCount
• GeomBranchFirst
• GeomBranchLast
• GeomBuffer
• GeomCenter
• GeomCenterInner
• GeomCenterWeight
• GeomClip
• GeomContains
• GeomConvertToArea
• GeomConvertToLine
• GeomConvertToPoint
• GeomConvexHull
• GeomCoordCount
• GeomCoordXY
• GeomCoordXYZ
• GeomDistance
• GeomDistancePoint
• GeomDistancePoint3
• GeomGml
• GeomHasCurves
• GeomHasZ
• GeomIntersects
• GeomIsArea
• GeomIsLine
• GeomIsNormalized
• GeomIsPoint
• GeomJsonGeo
• GeomLength
• GeomLinearize
• GeomMakeCircle
• GeomMakePoint
• GeomMakePoint3
• GeomMakeRect
• GeomMakeRectDiagonal
• GeomMakeSegment
• GeomMakeSegment3
• GeomMakeTriangle
• GeomMakeTriangle3
• GeomMergeAreasPair
• GeomMergeLinesPair
• GeomMergePointsPair
• GeomNormalize
• GeomNormalizeTopology
• GeomOrtho
• GeomOverlayAdjacent
• GeomOverlayContained
• GeomOverlayContaining
• GeomOverlayIntersecting
• GeomOverlayTopologyIdentity
• GeomOverlayTopologyIntersect
• GeomOverlayTopologyUnion
• GeomOverlayTopologyUpdate
• GeomOverlayTouching
• GeomRemoveCurves
• GeomRemoveZ
• GeomRotate
• GeomScaleShift
• GeomScaleShiftZ
• GeomScaleToSystem
• GeomScaleToSystemCff
• GeomScaleToUnits
• GeomScaleToUnitsCff
• GeomSegmentize
• GeomSetZ
• GeomSmooth
• GeomToBranches
• GeomToCoords
• GeomToSegments
• GeomToShapes
• GeomToShapesEsri
• GeomTouches
• GeomTriangulate
• GeomTriangulateLines
• GeomType
• GeomUnionAreasPair
• GeomUnionBoxesPair
• GeomVoronoi
• GeomVoronoiLines
• GeomVoronoiPoints
• GeomWithin
• GeomWkb
• GeomWkt
• Hypot
• J0
• J1
• Jn
• Lgamma
• Log
• Log10
• Log1p
• Log2
• NullIf
• PragmaValue
• Rcbrt
• Round
• RoundDecs
• Rsqrt
• Selection
• SelectionForWindow
• SelectionIsEmpty
• SelectionIsInverted
• SelectionKeys
• Sign
• Sin
• Sinh
• Sqrt
• StringCompareCollate
• StringCompareKeyCollate
• StringContains
• StringContainsCollate
• StringEndsWith
• StringEndsWithCollate
• StringEscape
• StringEscapeEncode
• StringEscapeJson
• StringFind
• StringFindCollate
• StringFindNth
• StringFindNthCollate
• StringGmlCoordSystem
• StringGmlGeom
• StringJsonArray
• StringJsonBoolean
• StringJsonGeoCoordSystem

• StringJsonGeoGeom
• StringJsonNumber
• StringJsonObject
• StringJsonValue
• StringLength
• StringPadEnd
• StringPadStart
• StringRegexpCount
• StringRegexpFind
• StringRegexpFindNth
• StringRegexpMatches
• StringRegexpReplace
• StringRegexpReplaceNth
• StringRegexpSubstring
• StringRegexpSubstringNth
• StringReplace
• StringReplaceCollate
• StringReplaceNth
• StringReplaceNthCollate
• StringReverse
• StringSoundex
• StringStartsWith
• StringStartsWithCollate
• StringSubstring
• StringSubstringLen
• StringToCharacters
• StringToJsonArrayValues
• StringToJsonObjectValues
• StringToLowerCase
• StringToLowerCaseCollate
• StringToRegexpMatches
• StringToTitleCase
• StringToTitleCaseCollate
• StringToTokens
• StringToUpperCase
• StringToUpperCaseCollate
• StringTranslate
• StringTrim
• StringTrimEnd
• StringTrimStart
• StringUnescape
• StringUnescapeDecode
• StringUnescapeJson
• StringWktGeom
• SystemCpuCount
• SystemGpgpuCount
• SystemGpgpus
• Tan
• Tanh
• Tgamma
• TileAbs
• TileAcos
• TileAcosh
• TileAsin
• TileAspect
• TileAtan
• TileAtan2
• TileAtanh
• TileBgrHcy
• TileBgrHsi
• TileBgrHsl
• TileBgrHsv
• TileBlur
• TileBlurDirection
• TileBlurGaussian
• TileCbrt
• TileCeil
• TileChannel
• TileChannelCount
• TileChannels
• TileChannelsConcat
• TileCombine
• TileCompare
• TileContrast
• TileCos
• TileCosh
• TileCut
• TileCutBorder
• TileCutRect
• TileEdges
• TileEdgesDirection
• TileErf
• TileErfc
• TileExp
• TileExp10
• TileExp2
• TileExpm1
• TileFill
• TileFloor
• TileFloorDecs
• TileFract
• TileFractDecs
• TileHcyBgr
• TileHsiBgr
• TileHslBgr
• TileHsvBgr
• TileHypot
• TileJ0
• TileJ1
• TileJn
• TileLgamma
• TileLog
• TileLog10
• TileLog1p
• TileLog2
• TileMakeNew
• TileMaskExtract
• TileMaskReplace
• TileMax
• TileMin
• TileNoise
• TileRcbrt
• TileRound
• TileRoundDecs
• TileRsqrt
• TileSharpen
• TileSign
• TileSin
• TileSinh
• TileSlope
• TileSqrt
• TileTan
• TileTanh
• TileTgamma
• TileToValues
• TileToValuesX2
• TileToValuesX3
• TileToValuesX4
• TileTrunc
• TileTruncDecs
• TileUpdatePyramids
• TileY0
• TileY1
• TileYn
• Trunc
• TruncDecs
• UuidMakeNew
• ValueCount
• ValueMax
• ValueMin
• ValueSequence
• VectorBgrHcy
• VectorBgrHsi
• VectorBgrHsl
• VectorBgrHsv
• VectorHcyBgr
• VectorHsiBgr
• VectorHslBgr
• VectorHsvBgr
• VectorMakeX2
• VectorMakeX3
• VectorMakeX4
• VectorValue
• VectorValues
• Y0
• Y1
• Yn