> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firebolt.io/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.firebolt.io/feedback

```json
{
  "path": "/reference-sql/functions-reference/aggregation/sum",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

> Reference material for SUM

# SUM

Calculates the sum of an expression.

## Syntax

```sql theme={"theme":{"light":"github-light","dark":"github-dark"}}
SUM ([ DISTINCT ] <value>) [FILTER ([WHERE] <condition>)]
```

## Parameters

| Parameter     | Description                                                       | Supported input types |
| :------------ | :---------------------------------------------------------------- | :-------------------- |
| `<value>`     | The expression used to calculate the sum.                         | Any numeric type      |
| `<condition>` | An optional boolean expression to filter rows used in aggregation | `BOOL`                |

Valid values for `<value>` include column names or expressions that evaluate to numeric values. When `DISTINCT` is being used, only the unique number of rows with no `NULL` values are summed.

## Return Types

`NUMERIC`

## Precision and Determinism

Applying `SUM` to REAL and DOUBLE PRECISION is subject to [floating point arithmetic accuracy limitations](https://en.wikipedia.org/wiki/Floating-point_arithmetic#Accuracy_problems) and its resulting error.
This error may add up when aggregating multiple values.

The order of operations while computing the aggregate is non-deterministic.
This can lead to varying total floating point error when running a query multiple times.
If this is not acceptable for your use-case, aggregate on [NUMERIC](/reference-sql/data-types/numeric) data instead.

## Examples

**Example**

This code example uses the following `tournaments` table:

| name                          | totalprizedollars |
| :---------------------------- | :---------------- |
| The Drifting Thunderdome      | 24,768            |
| The Lost Track Showdown       | 5,336             |
| The Acceleration Championship | 19,274            |
| The Winter Wilderness Rally   | 21,560            |
| The Circuit Championship      | 9,739             |
| The Singapore Grand Prix      | 19,274            |

```sql theme={"theme":{"light":"github-light","dark":"github-dark"}}
SELECT
	SUM(totalprizedollars)
FROM
	tournaments
```

**Returns**

`99,951`

**Example**

For the following code example, since both the Singapore Grand Prix and The Acceleration Championship have the same total prize of `19,274`, only one of these values in this sum in included:

```sql theme={"theme":{"light":"github-light","dark":"github-dark"}}
SELECT
	SUM (DISTINCT totalprizedollars)
FROM
	tournaments
```

**Returns**

`80,677`