DBCCMD validates the input parameters. If the command is used in the background, any response is sent to the TDP console log. If the command is run in the foreground, DBCCMD responds with a return code or an error code. Possible return and error codes are as follows:
| Return Code | Meaning |
|---|---|
| 0 | Command was successfully sent to target TDP. |
| 4 | Required input parameter is missing or invalid. |
| 8 | Required tdpid argument is missing or invalid. |
| 12 | Required command text argument is missing. |
| 264 | Target TDP does not support the command facility. |
| 280 | Target TDP was not found. |
| 282 | Target TDP was not available. |
Since DBCCMD essentially uses the same interface that CLIv2 uses to send work to TDP, the DBCCMD interface performs the same validation as it does for any CLIv2-to-TDP request. Any error codes returned other than those listed above would, therefore, indicate an internal error in DBCCMD.