Data Source=myServer\myInstance: The server name is "myServer" and the instance name is "myInstance"Ĭomparing this string with the one in the connection string in the ActiveX call, we can see that there is an extra string Integrated Security=SSPI. As one of the most popular database servers used in all types of organizations, Microsoft SQL Server finds itself as a required data source for many types of.
Initial Catalog=myDatabase: The name of the database on the server is "myDatabase".
User ID=myUsername: The user name is "myUsername".
#Vb6 sql server connection string windows authentication password#
Persist Security Info=True: You will allow saving the password (password is saved in the udl file).
User ID : N/A: The SQL Server login account. This will automatically move forward as the client and server components are upgraded. When set to Latest, the latest version than this client-server pair can handle is used. Now I want to connect to a Server 2005 db, using Windows authentication if possible. It connected to Server 2000 database using server authentication. No conversions are made for the current version of ADO.NET. I have an old Word 2000 macro (VB6 script).
Password=myPassword: The password is "myPassword" When set to SQL Server 2005, the SQL Server 2005 type system is used.
Provider=SQLOLEDB.1: The OLE DB provider is "Microsoft OLE DB Provider for SQL Server".
We can interpret the string in the following way: Provider=SQLOLEDB.1 Password=myPassword Persist Security Info=True User ID=myUsername Initial Catalog=myDatabase Data Source=myServer\myInstance Chosing the Microsoft OLE DB Provider for SQL Server option, you could proceed through the rest of the connection details with the following details:Īfter clicking OK, you would generate a UDL file, containing the following string: SolutionWhen you create a UDL file from a LabVIEW VI, you would access that from the menu Tools✼reate Data Link.