NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

NI Teststand Database logging.

Solved!
Go to solution

Hi,

 

I use NI Teststand to manage my SQL database connection as I am no expert in SQL management. But I have run into a problem.

 

In one of my tests I disable my LAN card in my computer resulting in a break in the LAN and SQL connection. This is expected. But when I enable my LAN card again it takes allmost 2 min before the SQL connection is up again.

 

Is there a way to force Teststand to connect to database again?

 

/Kasper

0 Kudos
Message 1 of 6
(3,953 Views)

It takes some time until you computer re-connects to the LAN card. Then TestStand has to detect the card is back etc... so it seems like expected behaviour to me.

 

Are you using on the fly reporting? if not maybe this is not an issue if your test sequence lasts more than those 2 min

Rodéric L
Certified LabVIEW Architect
0 Kudos
Message 2 of 6
(3,948 Views)

Hi Rodéric 

 

Thank you for the fast reply.  But in my case the only thing I am waiting for is teststand to reconnect to the sql database.

Is there a way to force teststand to connect to the database faster? I allready know that the network is up and running fine. 

 

/Kasper

0 Kudos
Message 3 of 6
(3,941 Views)

- and Im not using "on the fly" logging. 🙂

0 Kudos
Message 4 of 6
(3,937 Views)

Kasper -

When you say it does not work, what are the symptoms, are you getting an error, is it just hanging for a period of time until the connection is complete?

 

Are you reenabling the LAN card in between UUT loops for a single execution, or are you starting a new execution?

 

If you are doing this while the execution is running, the connection reference to the database is stored as a hidden property on the Execution object itself. The name of the property contains the name of the schema that you are using. You might be able to set that reference to nothing and/or delete the property.

 

If starting a new execution, then the issue is likely more that SQL client component is causing the delay.

 

- Scott

Scott Richardson
https://testeract.com
Message 5 of 6
(3,915 Views)
Solution
Accepted by topic author Kasper Friang Larsen

Hi Scott,

 

You were right this was the solution:

 

"If you are doing this while the execution is running, the connection reference to the database is stored as a hidden property on the Execution object itself. The name of the property contains the name of the schema that you are using. You might be able to set that reference to nothing and/or delete the property."

 

Thank you. 🙂

0 Kudos
Message 6 of 6
(3,883 Views)