NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Batch model Access database logging optimalisation

Hi All,

 

I developed a test program in TestStand 4.1 using 80 testsockets via the batch model. Results are logged to a Microsoft Access database file. Logging the results takes a few minutes: this is longer than the actual test. When i look into the Batch model i see that each testsocket calls the ActiveX component TSDBLog one by one. Watching the folder with the Access database I see the lock file appearing and disappearing, meaning that each testsocket opens and closes the file. Is it possible to open the database file by the first testsocket and close it with the last to improve the logging time?

 

In the "Database Options" at the tab "Data Link" I found an option "Share Data Link Between Executions" which is checked. What is exactly the purpose of this option?

 

 

0 Kudos
Message 1 of 2
(2,612 Views)

Hi,

The batch model instantiates an execution for each test socket being used. When you select that checkbox to Share Data Link, it means that each execution is provided with the same link, as opposed to having separate references to the same source. This prevents there being issues with access to a shared database, either when you are using multiple concurrent executions or if two results plug-ins are accessing the same database.

 

Is there something else you needed? Is the time that the database takes to write causing major issues?

 

Nico

--------
Nico
Systems Engineer

Certified TestStand Architect Certified LabVIEW Architect

0 Kudos
Message 2 of 2
(2,514 Views)