SQL database schema issues: Generic vs. SQL Stored Proc

[Scott_Richardson · Accepted solution]

Corey -

The validation feature does not know how to query the database to look inside the stored procedures to determine what tables it uses, so it assumes that the name of the TestStand schema will correspond to a specific table name, and this generates the warning that you see.

The STEP_NUMERICLIMIT* statements write to the PROP_RESULT and PROP_NUMERICLIMIT tables, and the PROP_IVIWAVE* statements write to the PROP_ANALOGEWAVEFORM table. If you have not already done so, you can find some of this information on the "Default TestStand Table Schemas" help topic.

Once you create your table using SQL script, you should see the tables and stored procedures as shown in the attached image. You should then be able to log to the database tables from TestStand assuming that you have created the correct expression for the connection string.

[Corey.Rotunno]

Scott,

  Yep, that's exactly what my database looks like. Thanks for the explanations and the time it took to get there.

Much appreciated,

[Skoda3]

Stored procedure InsertPropResult writes data to PROP_RESULT and PROR_NUMERICLIMIT tables...

We have created .sql file and now we get this warning:

Multiple instances of 'CREATE PROCEDURE' SQL commands are present for the procedure 'InsertPropResult'. Please retain only one valid instance of the command and remove the others.

So if we remove instance of procedure that writes to PROP_RESULT table, we cannot write to PROP_NUMERICLIMIT table.

Is it possible to rename stored procedure InsertPropResult as InsertPropResult1 and InsertPropResult2 so that it will work for both tables?