@anon67236913 @jtbatzer Thank you both for this clarification! I did this and it still didn’t work. According to SonarQube’s documentation, that .dll file is only needed if integrated security is being used, which I am not currently trying to use, however I did want to use this in the future, so thank you for helping me with that piece (more on that later).
Suspecting something is missing from SQ’s documentation, I looked up Microsoft’s article on JDBC connections (Building the connection URL - JDBC Driver for SQL Server | Microsoft Learn) and found “instanceName” was missing from their page: https://docs.sonarqube.org/latest/setup/install-server/
Sure enough, I changed my server.properties from…
sonar.jdbc.url=jdbc:sqlserver://localhost:1433;databaseName=sonar
to…
sonar.jdbc.url=jdbc:sqlserver://localhost;instanceName=SONAR;databaseName=sonar
… it finally worked.
To prove that my server.properties change was the root of the issue all along, I removed the mssql…dll file from my Java bin folder and tried again and still got a successful connection. I then tried integrated security and it didn’t work without the .dll file, as expected. I re-added the .dll and tried agian with integrated security and it works now as well (thanks again for helping me with that piece).
Any SonarSource employees that see this, please add instanceName to the jdbc connection string documentation or at least have some examples of working connection strings so people can reference them. This should not have taken me this long to figure this out.