How to create a connection string for CVI/SQL Toolkit when connecting to SQL Server 2008

[freighTrain]

Champ11,

The post you are responding to was from almost 3 years ago - you might be better off sending TJANK a private message or starting a new thread.

[urhisam]

Hello sir..... I am new to Labview ....Will u give a basic idea regarding  how to connect SQL databse application through LabView..... ?

[urhisam]

Let me know..how to Connect SQL databse with LabView....?

[Wolfgang]

You'd better ask in the LabVIEW forum here

[Little_Mole]

Yes, this is really an old post.. but as I have the same problem,.. by googling.. it ends up at this post..and there is no exact example of solution. Here is my working connection string as for a guide line used on CVI 2017, running MS SQL 2008 R2, with a named instance (DB1)

DBConnect("Driver={SQL Server};Server=127.0.0.1\\DB1;Database=dbname;Uid=sa;Pwd=lalala;");

Something like "ODBC;Driver={SQL Server} .." leads me to different path.. which does not work for me. and since I 'm running a named instance, "Server=ip\\instance_name" is mandatory.

Roadmap before success: try creating a working User or System DSN in ODBC manager. Turn on ODBC trace log. Use DBConnect in CVI to connect to the DSN successfully. Then compare the trace log with your failed DSN-less DBConnect string.. check/compare the [provider]..[driver].. path

Readjust the connection string...

[Little_Mole]

Forgot to mention that, the above working connection string require enabling TCP/IP protocol for the named instance too. With different connection string that leads to other provider/driver, it mays also lead to other protocol such as named pipe, which might require you to readjust the 'server=xxxx' part.