It is an SQL database and there is no password as we use a general read only account. I don't have the client software installed on the machine.
Technically speaking most databases that you connect to remotely are SQL databases. But they may be running an Oracle, Microsoft SQL Server, or Maria DB/MySQL engine or several other less common ones. And each of them needs a different ADO.NET/OLE-DB/ODBC driver, so it is actually important to specify the type of SQL engine it is running on.
You may have meant to say MS SQL Server, but that wasn't clear from your message.
In order to access any of these servers from your computer through the Database Connectivity Toolkit you will need to have the according database driver installed. This can be either an OLE-DB or ODBC based driver. You also have to watch out about the bitness. In order to use the Database Connectivity Toolkit you would need to use LabVIEW 32 bit and an according 32 bit database driver. If you are on 64 bit Windows you will need to run odbcad32.exe in C:\Windows\SysWOW64 in order to configure this. The ODBC Administrator that gets started from the Control Panel is the 64 bit version which only configures 64 bit drivers.
As others have mentioned, you will also need the type of SQL Server (Oracle, MySQL, SQL Server, MS Access, etc.) to determine the driver to use for connecting.
The input to the Database connect vi can either be a UDL string, or a path to a UDL file.
To use a file just create a new text document (Where you would keep other config files for this program) and give it the extension .udl, open the file and the Data Link Properties window will open to allow you to configure the connection, save and pass the filename to the database connect vi when you run the software.
The udl connection string can have a couple of different settings but the format itself is fairly straightforwards, you might want to check out ConnectionStrings.com for examples and values.