# Run Sensitive Data Discovery on Data Sources

## Prerequisite

[Sensitive data discovery must be enabled](/saas/~/changes/l3NnvynMHxi6VvqRtJhK/discover-your-data/data-discovery/how-to-guides/enable-sdd.md).

## Command Overview: `immuta sdd run`

This command allows you to run SDD on specific data sources or all data sources in your instance of Immuta.

### Options

Use these options to get more details about the `sdd run` command or any of its subcommands:

* `-h`
* `--help`

```bash
$ immuta sdd -h
Run Sensitive Data Discovery with provided options

Usage:
  immuta sdd run [datasourceName(s)] [flags]

Examples:
# run SDD as a dry run on the specified data sources
$ immuta sdd run "Datasource One" "Datasource Two" --dryRun --template "someFramework"
# run SDD on ALL data sources in immuta
$ immuta sdd run


Flags:
  -d, --dryRun                  No updates will actually be made
  -f, --force                   Do not prompt for confirmation when attempting to run sdd on all data sources
  -h, --help                    Help for run
  -o, --output json | yaml      Output format
      --outputTemplate string   Format the response using a Go template
  -t, --template string   Run SDD with this template, can only be used with the dryRun flag
  -w, --wait int                The number of seconds to wait for the SDD job(s) to finish. Default is until the SDD job(s) finish (default -1)

Global Flags:
      --config string    Config file (default $HOME/.immutacfg.yaml)
  -p, --profile string   Specifies the profile for what instance/api the cli will use (default "default")
```

## Run SDD on Specific Data Sources

Run `immuta sdd run <dataSourceName> [flags]`, naming the data source you want to run SDD on. The options you can specify include

* `-d`, `--dryRun`: No updates will actually be made.
* `-f`, `--force`: Do not prompt for confirmation when attempting to run SDD on all data sources.
* `-h` or `--help`: Get more information about the command.
* `-o` or `--output json | yaml`: Specify the output format.
* `--outputTemplate string`: Format the response using a Go template.
* `-t`, `--outputTemplate string`: Run SDD with this framework. This flag can only be used with the `dryRun` flag.
* `-w`, `--wait int`: The number of seconds to wait for the SDD job(s) to finish. Default is until the SDD job(s) finish (default -1).

### Example

The example below illustrates a user running SDD on a single data source.

```bash
$ immuta sdd run "Credit Accounts"
Running SDD
Credit Accounts  06b71830-aebc-11ec-970b-51ffefcbfd0c  completed
```

## Run SDD on All Data Sources

1. Run `immuta sdd run`. The options you can specify include
   * `-d`, `--dryRun`: No updates will actually be made.
   * `-f`, `--force`: Do not prompt for confirmation when attempting to run SDD on all data sources.
   * `-h` or `--help`: Get more information about the command.
   * `-o` or `--output json | yaml`: Specify the output format.
   * `--outputTemplate string`: Format the response using a Go template.
   * `-t`, `--outputTemplate string`: Run SDD with this framework. This flag can only be used with the `dryRun` flag.
   * `-w`, `--wait int`: The number of seconds to wait for the SDD job(s) to finish. Default is until the SDD job(s) finish (default -1).
2. Confirm that you want to run SDD on all data sources.

### Example

```bash
$ immuta sdd run
Running SDD
Started 8 SDD jobs
```


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.immuta.com/saas/~/changes/l3NnvynMHxi6VvqRtJhK/developer-guides/the-immuta-cli/manage-sensitive-data-discovery/sdd.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.