Have you configured the freetds driver to include the definition of the database server?
Lookup KA353505 which refers to the BPPM ETL but is similar.
In short, you need to create an entry in
and use that to configure the database connection.
Please notice that freetds might not work with NT authentication, SQL-Server native authentication is recommended.
Let me know if it helps,
1 of 1 people found this helpful
Thank you for your help, Renato. After some back and forth, this is what finally fixed it for me.
Configured freetds.conf with the following:
host = <<Server Name>>
instance = <<SQL Instance Name>> ; In my case they were the same
port = <<Port #>> ;In my case, the above instance was listening on a non-standard port
tds version = 7.0 ;this setting didnt' seem to matter
At this point, I ran the command-line utility as described in the KA article and it failed. I changed my username to <<Domain>>\\<<Service Account Name>> (note the escape character) to get it to function properly.
After reviewing the testconnection.txt file that was output by the command-line test, I noticed that I was being put in MASTER. I asked our DBA to make the default database to our Solarwinds DB. This appeared to have me log in directly to where the ETL needed to be.
I suspect, however, that if I need to do an ETL from another dB on the same dB server that I'll need to find a better solution.
I then reconfigured the ETL to match my freetds.conf settings as described. Simulations continued to fail until Renato pointed out that I didn't need the escape character on the ETL side.
The simulation ETL is currently running and, assuming that it completes successfully, I'll run a full import later today.