MS SQL Server adapter -U/-P flags passed in SQL Server connection string

[michael-duren]

vim.g.dbs = {
	{
		name = "DEV",
		url = "sqlserver://HOSTNAME:1433/DBNAME",
	},
}

Connecting to db DEV...
Error detected while processing function <SNR>38_method[2]..43[30]..46[7]..17[16]..function <SNR>38_method[2]..43[30]..46[7]..17[15]..db_ui#notifications#error[1]..<SNR>42_notification[17]..<SNR>42_notification
_nvim_notify:
line   17:
Error connecting to db DEV DB exec error: Sqlcmd: The -E and the -U/-P options are mutually exclusive.

This happens regardless if I'm adding a connection manually or adding it to my config.
I'm using dadbod-ui, but if I just try the command I get the same output: The -E and the -U/-P options are mutually exclusive.
It seems to pass the -U/-P flags even though my connection string doesn't have a username and password and per the documentation it should add the integratedSecurity if I omit the username/pwd.

Supported query parameters are `authentication`, `secure` and
`trustServerCertificate`, which correspond to connection properties of the
same name. The `authentication` property is only supported when using
`go-sqlcmd`.

Is there something I'm doing incorrectly?

SQLCMD.EXE 16.0.1000… C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\SQLCMD.EXE

[cognitiveRobot]

@michael-duren did you manage to fix your issue? Can you please share the connection string format?

[michael-duren]

I did not. I don't know much vim script since I use neovim and lua so I haven't gone too deep into it.
Here's an example string:
sqlserver://:1433?database=&TrustServerCertificate=true

[cognitiveRobot]

@michael-duren thanks for your reply. Later found out that I can't connect to the server using sqlcmd from ubuntu linux with domain user account.

[jamrolls]

I spent all day working on figuring this one out. Same message about conflicting -E and -U/-P options being mutually exclusive. I was practically tearing my hair out debugging dadbod, trying to figure out how somehow it was passing an extra parameter that didn't appear to be in the executed command.

After several hours, I finally found the problem: sqlcmd is lying about its issue. You can reproduce this erroneous error mesage directly from the comand line, e.g. sqlcmd -S servername\instance -E -d databasename -i /tmp/Wh4T3v3R/140.sql — despite the fact that you have only passed -E, it will complain about using -U/-P also, due to what I guess must be a bug in sqlcmd.

The real problem is that it was unhappy about the input file path, /tmp/Wh4T3v3R/140.sql, as that path does not exist as far as sqlcmd is concerned; on Windows it's expecting something like C:\Temp\.... But, since I am using Git for Windows, dadbod/vim think they're running under linux and assume that that path is valid.

I might try and get a fix together into a pull request, but I'm ... not great with vimscript, so we'll see. I thought I'd at least try and document what I found, in case it helps someone else solve it!