Logging Additional Results to a Database in TestStand

Before using any of the methods described below, ensure that the Database model plugin is enabled.

Go to Configure » Results Processing, and verify that the Enabled checkbox for the Database plugin is selected.

Also confirm that the plugin is configured with a valid connection string and schema. By default, TestStand provides:

If you keep these defaults, you should be able to complete the steps below without issues.

For instructions on configuring the example database connection, refer to the following articles:

In this method, you add a dedicated step that logs a custom result directly to the database.

Results created this way are stored in the PROP_RESULT table.

Follow these steps to configure the MainSequence:

Add an Additional Results step type to your sequence file.
Select Add Custom Result.
Fill in the Name field with a string literal (using double quotes), and set Value to Log to the data you want to store.

Note: You may also use the value of a string variable to populate the Name field.
Run the sequence using Single Pass or Test UUT. After execution, the custom result will appear in the PROP_RESULT table.
Go to Configure » Result Processing…
Click Options.
In the Logging/Data Link Options tab, select View Data to open the TestStand Database Viewer.
Right‑click the PROP_RESULT table and select View Data.
(Optional) Hide unwanted columns so only NAME and DATA remain (right‑click a column → Hide This Column).
Alternatively, run the query below in the top panel of the viewer to return only the NAME and DATA fields:
```
SELECT NAME, DATA FROM [PROP_RESULT]
```
Use the Execute button (green play icon) to run the query. The results appear in the Results tab.

Select the step you want to log additional results from.
In the Step Settings pane, go to the Properties tab and select Additional Results.
Click +, then enter the Name and Value to Log fields as in Method 1.
Run the sequence using Single Pass or Test UUTs.
To view the logged data, follow the same steps used in Method 1:
- Configure » Result Processing…
- Options
- Logging/Data Link Options » View Data
- Open the PROP_RESULT table
You should now see a table containing both new and previously logged custom properties.
Note that the STEP_RESULT column shows the same value (e.g., 4) for both custom results, since they belong to the same step.
To filter results for that specific step, run:
```
SELECT NAME, DATA FROM [PROP_RESULT] WHERE STEP_RESULT = 4
```
(Your STEP_RESULT value may differ; confirm it in Step 6.)
You will now see only the results associated with that step.

Select the step.
In the Step Settings pane, go to the Module tab and configure your code module.
If the code module contains an output parameter you want to log, enable the checkbox under the Log column.

The step will now automatically include a corresponding Additional Result entry.
(Optional) Switch to the Properties tab and open Additional Results. You’ll see that the parameter has already been added.

TestStand appends the suffix [Out] to indicate this value comes from a code module output.
Run the sequence using Single Pass or Test UUTs.
To view the logged data, follow these steps (same as Method 1):
- Configure » Result Processing…
- Options
- Logging/Data Link Options » View Data
- Open the PROP_RESULT table

Use this query to locate your code‑module output result:

SELECT NAME, DATA FROM [PROP_RESULT] WHERE NAME = "Scaling Factor [Out]";

Environment