NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

UUT Result log in SQL database?

Hello All

 

I am facing a requirement where i want to log results of sequence execution[only the complete seq result and NOT step results] to SQL database BUT as and when the UUT_ID varies the entry should be made into a new column with the same name as UUT_ID. As of now whenever i execute a sequence with different UUT_ID, a new row gets added as a result.

 

Please reply back with your suggestions asap, as this very urgent for me 🙂

 

 

Regards

Nitin Goel

0 Kudos
Message 1 of 4
(3,547 Views)
I don't understand the schema you are trying to implement. If you want a new column for each UUT in the step results table, how can you possibly differentiate between each one when you query the database? A new row is the expected and normal behavior. I don't think I have ever heard of such a database design as the one you want to implement.
0 Kudos
Message 2 of 4
(3,542 Views)

Thanks for the information.

Actually, i want to get a new column added for test result of same sequence whenever it is executed with a different UUT_No and it is primarily because i have thousands of test cases in my test system and i want it in format as below:

 

              Build1       Build2        Build3    

Test1      Passed     Passed      Passed

Test2      Failed       Passed      Passed

and so on.

 

 

0 Kudos
Message 3 of 4
(3,539 Views)

But in my opinion, that's just a way to display the results - not a way to store the data. I also have thousands of test cases and tens of thousands of different UUT each month. Each UUT has a separate record (a unique row) and yet if I design a proper query and report format, I can show the results exactly like you have. The design of a relational database should not be the same as a report design, imho.

 

A database is designed to have unlimited rows (dependent only on storage space). I'm not sure a db can have unlimited columns. That would be something you could check with your dba. Dynamically adding a new column and doing an update to an existing row would probaby be much slower than just doing an insert.

0 Kudos
Message 4 of 4
(3,534 Views)