What MS SQL Server Express version should I install?

[pincpanter]

Hi, I'm planning to use MS SQL Express for my LabVIEW app under Windows 7.

There are 3 versions available on the MS site: 2005, 2008, 2012. My first choice is on the latest, however I wonder if there may be any reason to choose an earlier version.

Also I wonder if the installation could conflict some way with the SQL Server Express 2005 the DSC module uses.

Sorry for my rather dumb questions but I'm not very strong on the relational databases subject.

Thanks a lot for any comment.

[Ranjeet_Singh]

Go for 12 only as other application which uses 05 should be compatible with 12 also

[pincpanter]

Thank you Ranjeet for the answer.

In your opinion it's better to install them side-by-side or update the existing server (on the development machine)?

[SunshineDesign]

If it were me, I'd get ride of the old 2005 version and just go with SQL Server Express 2012 to have all the latest features, bug fixes and interface issues resolved with Win7 & Win 8, which you may not get with the older versions. I use SQL Server 2012 exclusively now.

[Cla_Cup]

Hi Paolo,

I think that MS SQL Server 2012 will be the best choice.

What version of LabVIEW are you currently using?

Best Regards.

CLA_CUP

NI ITALY

[Ranjeet_Singh]

I think it will update with older version. As told earlier install the newer version is always better then older as it will be used in future also.

[pincpanter]

Thanks for your answers. I installed SQL Server 2012 Express.

CLA_CUP: my current LV version is 2011.

[Ranjeet_Singh]

Go ahead

[plf]

Ranjeet...

I am using SQLServer Express 2012 with TestStand 2012 and having no luck getting TestStand to log to the catalog that I have created based off of the standard NI SQL scheme. 

When creating the tables using the build sql file I found that...

I ran ito issues with the 'constraint' SQL commands TestStand was using:

CONSTRAINT STEP_RESULT_FK FOREIGN KEY (UUT_RESULT) REFERENCES  (ID))

this must actually be:

CONSTRAINT STEP_RESULT_FK FOREIGN KEY (UUT_RESULT) REFERENCES UUT_RESULT (ID))

Note.... the 'UUT_RESULT' infront of (ID), without this the statement fails.

I had to correct all the constraint commands in order to get the tables built.

Now when I try to use the catalog to log data using TestStand I get...

An error occurred calling 'LogResults' in 'ITSDBLog' of 'zNI TestStand Database Logging'
An error occurred executing a statement.
Schema: SQL Server Stored Proc (NI)
Statement: UUT_RESULT.
Description: Could not find stored procedure 'InsertUUTResult'.
Number: -2147217900
NativeError: 2812
SQLState: 42000
Reported by: Microsoft OLE DB Provider for SQL Server

Source: TSDBLog

The procedure is present so I am confused. 

FYI... I am currently using TestStand in eval mode as I am waiting on delivery, could the eval mode be the issue???

Any help would be greatly appreciated. I have done this before with TestStand 3.5 and SQL Server 2008 with no problems so I am confused why it not working now.

Pete

[LabBEAN]

Gist mentions the "UUT Result" command edit you found here, but that thread is sort of dated.  One idea is to start a new topic since this thread is likely only read by people with an opinion about SQL Server versions.  If you think that NI should fix the broken Build .SQL file button that may be causing your error, me too.