11-14-2013 10:39 PM
Hi all,
I tried to submit this through the official support channel, but ran into this roadblock. So, I'm reporting the issue here.
=================================================
I wanted to set up TestStand to log results to an SQL Server 2008 R2 database. I followed the instructions at http://zone.ni.com/reference/en-XX/help/370052M-01/tsfundamentals/infotopics/database_logging/
I tried to run C:\Program Files\National Instruments\TestStand 2013\Components\Models\TestStandModels\Database\SQL Server Create Generic Recordset Result Tables.sql However, SQL Server reported that the script contains syntax errors.
To fix the issue, I had to modify the script (replace "//" with "--", and replace "~" with ";") before running it.
It looks like other scripts in this folder have syntax errors too. Please fix the SQL scripts shipped with TestStand.
11-15-2013 09:22 AM
JKSH -
Can you please indicate in what application you ran the scripts?
11-15-2013 09:24 PM - edited 11-15-2013 09:26 PM
11-18-2013 08:32 AM - edited 11-18-2013 08:32 AM
Hey JKSH,
Thanks for reporting this--we've filed an internal report for one of our developers to examine the syntax of our SQL files.
In the meantime, it sounds like you were able to work around the issue by changing the characters in the scripts, but have you run into any other problems using the scripts? I'd be happy to help out in any way I can. Just let us know if there's anything we can do to assist!
11-18-2013 07:34 PM
09-26-2014 01:38 AM
09-29-2014 07:13 AM
You are correct, the script files and the Database Viewer application in 2014 still do not support default SQL delimiter syntax supported by specific DBMS SQL applications, but we would like to fix this in a future major release.
09-29-2014 08:49 PM
09-30-2014 12:51 AM
Hi JKSH,
Yes, we have noticed this too and when we fix this issue, we will update both the comment and the command delimiter characters to match the default values in the different DBMSs we support.
10-23-2015 09:54 AM
Not only does TestStand 2014 ship with invalid scripts, but it appears that the scripts do not even create all of the tables that are defined in the schema
For example STEP_NUMERICLIMIT1 and STEP_NUMERICLIMIT2 are not created.
Are there more up to date versions of these scripts?
Yes, it is not that hard to modify , but not everyone will know how to do that and the scripts really should work out of the box