SQL for ArcGIS Pro is built on Manifold's Radian® spatial database engine, the fastest, automatically parallel, desktop spatial SQL engine ever created.
The engine is built into SQL for ArcGIS Pro and totally automatic, so it's easy to use. Launch the add-in from ArcGIS Pro and the SQL console looks like any other desktop dialog with no admin worries, no configuration, and no need to write parallel code. Use ordinary SQL and the engine automatically parallelizes it for execution on all CPU threads available, plus automatic use of parallel GPU as well. Super!
SQL for ArcGIS Pro parallelizes and executes queries with a very high degree of modularity:
Big tasks automatically get split into small tasks, which get sent to different computation nodes using Directed Acyclic Graph (DAG) analytics. SQL for ArcGIS Pro does that optimization automatically.
But SQL goes much further than use of homogenous nodes.
Some of those nodes, potentially many thousands of nodes, can be Nvidia GPU cores, and those GPU cores can be different types of cores from different GPUs.
Some of those nodes, also potentially thousands but more likely only a few dozen or few hundred, can be CPU cores. Computational nodes also can be external databases like Oracle, SQL Server, PostgreSQL, or other databases.
The query engine will split the work optimally between any and all such nodes so that they all run in parallel. All that is included in every SQL for ArcGIS Pro license at no extra cost.
In addition to the query engine, SQL for ArcGIS Pro has a big roster of built-in SQL functions, both spatial and non-spatial, which all work within that parallel architecture.
All that parallelism happens automatically with no need for any parallel coding or manual setup of tasks. Write the SQL you already know and SQL for ArcGIS Pro executes it as if a team of experts
had parallelized it for you. No need for weeks or months of scary effort, like standing up a HADOOP application, that older tools require.
"I went from only being able to generate watercourses/watersheds on relatively small DEM's to being able to generate watercourses/watersheds on SRTM data for the whole of the New Zealand mainland in 10 mins and 20 mins respectively on my 5 year old machine. Amazing work!" - Forum post.
Everything you need for world-class spatial SQL magic with file geodatabases is built into SQL for ArcGIS Pro, with no need to install and maintain a separate DBMS. SQL for ArcGIS Pro also has perfect support for popular enterprise DBMS packages as well, but you don't have to use an external DBMS to get vast capacity and blistering speed. All that is built into SQL for ArcGIS Pro.
SQL for ArcGIS Pro is so fast and so powerful for database work that many people use SQL for ArcGIS Pro for data science and DBMS ETL having nothing to do with GIS: they like the speed, power, flexibility, point-and-click tools, SQL sophistication, and ease of use the add-in delivers for database exploration, analytics, and manipulation.
SQL for ArcGIS Pro unleashes the full power of all the CPU cores in your system and automatically launches massively parallel computations using thousands of available GPU cores for supercomputer computational performance unmatched by any other non-parallel GIS or spatial engineering tool.
This isn't marketing hype: calculations that take minutes in Arc without SQL for ArcGIS Pro can often be done in seconds in SQL. Insist on the real thing: automatic, parallel computation with no parallel coding required. SQL for ArcGIS Pro is the real deal: Nothing else on the desktop, at any price, comes close.
"Input: 220803 areas (coord count 4 to 841654, often highly convoluted). Output: 29306396 convex areas. Incredibly fast.." - Forum post on convex decomposition of polygons, in SQL for ArcGIS Pro an easy function.
Add the world's best desktop, parallel spatial SQL to the world's foremost desktop GIS package to get these outstanding benefits:
- Massively Faster Speed - Get done in seconds what takes minutes in Pro without parallel SQL. Running all cores and all threads in your computer is way faster than running only one core and one thread, and typically 20 to 50 times faster than partial parallelism as available in Spatial Analyst tools. When GPU parallelism fits a task, SQL for ArcGIS Pro can often run 200 times faster than Pro without SQL.
- Zero User Effort - SQL for ArcGIS Pro automatically uses all cores and all threads with no need for users to write specialized parallel code. Life doesn't get any easier than zero effort.
- Works Everywhere - Everything in SQL for ArcGIS Pro is parallel, including geoprocessing, SQL, computation, and everything else. You don't need to think about it. SQL works automatically parallel, giving faster computation and way faster action everywhere.
- Zero Cost - You've already paid for a processor that can run 8, 16, 24, 32 or more threads. It costs you zero extra to use all of those threads instead of just one thread.
- Never Waste Hardware - SQL for ArcGIS Pro automatically uses all multicore CPUs for parallel speed, whether they are 128-thread Threadrippers or older 4 core processors that can run only eight threads. Even older computers can run parallel with amazing speed that's usually way faster than the latest and greatest CPUs running single core.
- Effortless Hardware Upgrades - SQL for ArcGIS Pro automatically supports the latest CPUs, including upgrading a CPU or plugging in another CPU in a multi-socket motherboard. Just plug it in and it works, with SQL running parallel with even more threads.
- Enjoy Being Smart - In a world of inexpensive, 24 and 32 thread Ryzen CPUs you know in your heart it is not smart to fail to use all of those threads. Spatial Analyst tools usually run only eight or nine threads, while SQL runs them all to run much faster. Enjoy the excitement and deep gratification you get with speed ten or twenty times faster at zero extra cost.
- Better Data Science - Extremely fast, parallel SQL lets you try more sophisticated "what if" scenarios when doing data science. The freedom to try more scenarios, and more sophisticated scenarios leads to better insights faster.
- Save Money - Time is money. The biggest cost of doing GIS, ETL, or Data Science is the cost of your time, not low cost licenses. Nothing is as expensive as takes days of playing software developer to cobble up and debug in a python script what can be done in a few lines of SQL or with a point and click in Advanced mode in SQL for ArcGIS Pro.
- No Paywalls - Automatic CPU and GPU parallelism is built into every SQL for ArcGIS Pro license. You don't have to buy anything extra, install any options, or deal with annoying "you're not licensed for this" messages when you want a big job to run fast. All features are built into every SQL for ArcGIS Pro license. For only $245 you get it all.
Multi Core + Multi CPU
Decades ago in the 1990's all desktop computers had only one processor in their CPU chip.
Today's computers have many processors in their CPU chip. Some desktops even have multiple CPUs with many processors in each.
That gives your modern computer the power of many old-fashioned, single-processor computers,
but only if you run modern, multicore parallel software like SQL for ArcGIS Pro.
Non-parallel software still runs all computers as if they were old-fashioned 1990's
computers with only one core per task. No matter how modern your computer, non-parallel software imposes 1990's limits on you.
Your computer could have 20 processors in the CPU chip but non-parallel software will use only
one of those cores per task - just as if your computer was a 1990's computer.
SQL for ArcGIS Pro uses all cores in your computer for maximum power and maximum speed when executing SQL queries. The more cores you have, the bigger the gain. Even with only four cores and eight threads, SQL for ArcGIS Pro is way more powerful than single core software.
With twelve or sixteen cores, and 24 or 32 threads, nothing else comes close.
The graphs below show actual SQL for ArcGIS Pro performance in Windows 10 Resource Monitor using an inexpensive, 12-core / 24-thread, AMD Ryzen 9 3900X processor,
with and without parallel processing of an SQL function to transform images. SQL for ArcGIS Pro always uses all cores for a big process,
but other software can't do that. It might hop around from core to core, but just like the 1990's it never uses more than one core.
SQL for ArcGIS Pro: Full Power
No SQL: 1/20th Power
ArcGIS Pro without the SQL for ArcGIS Pro add-in is at best partially parallel, generally running parallel only when executing Spatial Analyst geoprocessing tools that have been parallelized, and then only typically to a maximum of eight or nine threads, not a full 24 threads as seen above. Writing python code in ArcPy also isn't parallel, so typically only 1/20th or so of the power of your 12 core system will be used. Doing the same jobs using SQL, in contrast, will run all threads to use 100% of your system's power.
Use All Of Your System's Power...
Does it make sense to spend a lot of money on a computer and then throw away most of what you bought?
- One Cylinder out of Eight? - Would you buy an automobile with an eight cylinder engine and then fill it with fuel that allowed only
one cylinder to work while seven cylinders did nothing?
- One Hour a Day? - Would you hire somebody that worked only one hour out of an eight-hour day but got paid for all eight hours?
- Why do that with software? If you wouldn't do that to your car, and if you wouldn't hire such a lazy worker, why do that to your computer?
If your computer has eight CPU cores, why use software that allows only one core to run a process while
seven cores stay idle?
... Not Just a Little
Software that can run only one core out of eight cores in your system wastes seven eighths of your system - almost all the power in
your system. Have you wondered why non-parallel packages are so slow with demanding jobs? One reason is they fail to use most of the computing power of
If you are running a modern processor like an Intel Core i7-6950X you have twenty hypercores. SQL for ArcGIS Pro uses all 20 hypercores. Automatically.
Non-parallel software will use only one hypercore and will waste 95% of the computer's power. Only SQL for ArcGIS Pro automatically uses all of the computer.
Even Faster: Multiple CPUs
If your system has multiple CPUs SQL for ArcGIS Pro will use all of the cores in every CPU.
Professional users in GIS and spatial data engineering can deploy desktop systems with two CPU sockets. Using a 16 or 20 hypercore Intel Core i7 CPU in each
of those two sockets will provide a total of 32 or 40 hypercores on the desktop. SQL for ArcGIS Pro will use them all for astonishing power.
Prices are plummeting on many-core CPUs. With 16 hypercore AMD Ryzen CPUs appearing in the $300 range a 32 core system using two such chips on the
motherboard becomes affordable for most professional users. $600 for 32 cores is way cheaper than $2200 or $3200. If you run SQL for ArcGIS Pro you can
enjoy blistering performance at absurdly low cost.
Parallel Processing - The Real Thing
Superior spatial data engineering requires parallel power, and real parallelism cannot be glued on to non-parallel code. It has to be built in from the ground up.
SQL for ArcGIS Pro was created from the ground up as an always-on, fundamentally parallel system, with parallel data management systems feeding massively parallel computation. The Radian database engine is a parallel engine and
Radian SQL automatically runs parallel by default. Every bit of SQL for ArcGIS Pro was designed and coded for fully parallel work, including all infrastructure, hundreds of functions
exposed for users and thousands of functions utilized internally. Zero weak links.
All of SQL for ArcGIS Pro is a true multicore, parallel processing system. SQL for ArcGIS Pro will automatically utilize multiple processors and multiple processor cores by parallelizing a task into
multiple threads for execution on all of the cores in your system. Given hyperthreading plus multi-core CPUs, even inexpensive desktops will have 8, 16, 32 or even
more CPU cores available. SQL for ArcGIS Pro will use them all, as the Resource Monitor graphs show above.
In addition to parallel processing using multiple CPU cores SQL for ArcGIS Pro also automatically launches massively parallel multiprocessing utilizing GPUs, potentially launching tasks
on thousands of GPU cores at once for true supercomputer computational performance, far beyond what can be achieved with multicore CPU alone and often hundreds of times faster than other software.
See the GPU Page for more.
SQL for ArcGIS Pro automatically parallelizes and dispatches hundreds of functions to GPGPU, with automatic fallback to parallelized tasks dispatched to multiple CPU cores if a GPU is not available.
It's all automatic and totally transparent with zero user effort required to use. Just do what you do and SQL for ArcGIS Pro handles all the parallel wizardry.
No Parallel Coding Required
You don't need to learn any parallel programming. SQL for ArcGIS Pro does it all for you with automatic parallelization.
Write the same SQL you already know and SQL for ArcGIS Pro automatically parallelizes it for execution. Point and click with
hundreds of SQL for ArcGIS Pro templates without any programming at all and those all run parallel too. Click open immense displays and SQL for ArcGIS Pro parallelizes
the rendering, parallelizes re-projections on the fly and everything else. SQL for ArcGIS Pro runs parallel on however many CPU cores you have.
Automatically. No parallel code required.
Cores, Hypercores and Threads
Cores and hypercores mean almost the same thing: both refer to using multiple physical or logical processors on the same silicon chip to give the power of multiple computers within one chip.
Cores usually means extra silicon circuitry, multiple copies of a processing unit. Hypercores is an Intel word for hyperthreading that gives a similar effect by leveraging
idle circuitry to provide the horsepower of extra processors. 20 hypercores are not as powerful as 20 physical cores, but they can be close enough to count them the same.
Windows counts them the same when it reports the number of CPUs in your system. Some chip vendors prefers the word threads to avoid using Intel's proprietary word. Microsoft's Task Manager uses the term logical processors to refer to what everbody else calls threads or hypercores. No worries - Whether you call them hypercores, threads, or logical processors, SQL for ArcGIS Pro can use them all for true manycore parallelism.
Buy Now via the Online Store
Buy SQL for ArcGIS Pro on the Online Store. The store is open 24 hours / seven days a week / every day of the year. Orders are processed immediately with serial number email sent out in seconds. Enjoy the world's best desktop spatial SQL today!