There is a command group 'az_dms_project_task'. This group of commands could 'manage tasks for a azure database migration service  classic  instance s project'. The group of commands has global parameter '--debug' which means 'Increase logging verbosity to show all debug logs.'. The group of commands has global parameter '--help -h' which means 'Show this help message and exit.'. The group of commands has global parameter '--only-show-errors' which means 'Only show errors, suppressing warnings.'. The group of commands has global parameter '--output -o' which means 'Output format.'. The group of commands has global parameter '--query' which means 'JMESPath query string. See <a href="http://jmespath.org/">http://jmespath.org/</a> for more information and examples.'. The group of commands has global parameter '--subscription' which means 'Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.'. The group of commands has global parameter '--verbose' which means 'Increase logging verbosity. Use --debug for full debug logs.'. This group contains a child command 'az_dms_project_task_create'.The syntax is: az dms project task create --database-options-json
                           --name
                           --project-name
                           --resource-group
                           --service-name
                           --source-connection-json
                           --target-connection-json
                           [--enable-data-integrity-validation]
                           [--enable-query-analysis-validation]
                           [--enable-schema-validation]
                           [--task-type]
                           [--validate-only]
                           [--validated-task-name]. The 1th example of the child command would be to use it to 'create and start a sql task which performs no validation checks', the syntax is: az dms project task create --database-options-json C:\CliFiles\databaseOptions.json -n mytask --project-name myproject -g myresourcegroup --service-name mydms --source-connection-json '{'dataSource': 'myserver', 'authentication': 'SqlAuthentication', 'encryptConnection': 'true', 'trustServerCertificate': 'true'}' --target-connection-json C:\CliFiles\targetConnection.json --task-type offlinemigration. The 2th example of the child command would be to use it to 'create and start a sql task which performs all validation checks', the syntax is: az dms project task create --database-options-json C:\CliFiles\databaseOptions.json -n mytask --project-name myproject -g myresourcegroup --service-name mydms --source-connection-json C:\CliFiles\sourceConnection.json --target-connection-json C:\CliFiles\targetConnection.json --enable-data-integrity-validation --enable-query-analysis-validation --enable-schema-validation --task-type offlinemigration. The parameter '--database-options-json' is required. It is used to database and table information. this can be either a json-formatted string or the location to a file containing the json object. see examples below for the format.. The parameter '--name -n' is required. It is used to the name of the task. a dms project task is the activity that performs migration related work. there could be multiple tasks associated with a project.. The parameter '--project-name' is required. It is used to the name of the project. dms project is a logical grouping that encompasses source database connection, target database connection and a list of databases to migrate.. The parameter '--resource-group -g' is required. It is used to name of resource group. you can configure the default group using `az configure --defaults group=<name>`.. The parameter '--service-name' is required. It is used to the name of the service. dms service is an azure instance that performs database migrations.. The parameter '--source-connection-json' is required. It is used to the connection information to the source server. this can be either a json-formatted string or the location to a file containing the json object. see examples below for the format.. The parameter '--target-connection-json' is required. It is used to the connection information to the target server. this can be either a json-formatted string or the location to a file containing the json object. see 'source-connection-json' for examples of connection formats.. The parameter '--enable-data-integrity-validation' is optional. for sql only. whether to perform a checksum based data integrity validation between source and target for the selected database and tables.. The parameter '--enable-query-analysis-validation' is optional. for sql only. whether to perform a quick and intelligent query analysis by retrieving queries from the source database and executing them in the target. the result will have execution statistics for executions in source and target databases for the extracted queries.. The parameter '--enable-schema-validation' is optional. for sql only. whether to compare the schema information between source and target.. The parameter '--task-type' is optional. the type of data movement the task will support. the supported types are: onlinemigration, offlinemigration. if not provided, will default to offlinemigration for sql, mongodb and onlinemigration for postgresql.. The parameter '--validate-only' is optional. for mongodb to cosmos db only. whether to run validation only and not run migration. it is mandatory to run a 'validate only' task before attempting an actual migration. once the validation is complete, pass the name of this 'validate only' task to a new task's 'validated task name' argument.. The parameter '--validated-task-name' is optional. (for mongodb to cosmos db only) when running a migration it is neceaary to pass in the name of a previously run 'validate only' task.. 