> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/soda-documentation/soda-v3/learning-resources/deprecated.md).

# Soda SQL and Soda Spark are now Soda Core

Soda SQL and Soda Spark have been deprecated and replaced by Soda Core.

The very first Soda OSS tools, Soda SQL and Soda Spark, served their community well since 2021. They have been deprecated. [Read more](https://www.soda.io/resources/introducing-soda-core-the-new-way-for-data-reliability) about the decision to deprecate and move forward with Soda Core.

* **Soda SQL** was the original command-line tool that Soda created to test for data quality. It has been replaced by Soda Core.
* **Soda Spark** was an extension of Soda SQL that allowed you to run Soda SQL functionality programmatically on a Spark DataFrame. It has been replaced by Soda Core configured to \[connect with Apache Spark]\(

  ).

## Documentation

The GitHub repository for the legacy tools has been archived but is still read-only accessible, including the documentation.

* [Soda SQL](https://github.com/sodadata/soda-sql/tree/main/docs)
* [Soda Spark](https://github.com/sodadata/soda-sql/tree/main/docs)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.soda.io/soda-documentation/soda-v3/learning-resources/deprecated.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.