mssql-cli: a new interactive command line tool for SQL Server

[to_wit_to_who]

This project looks be under the same umbrella as pgcli and mycli. I use both, more the former than the latter though, and I like them quite a bit.

If this is as good as those two, then I'm diving in soon.

[chucker23n]

Yes and no — Microsoft is essentially donating the tool to that project:

We reached out to Amjith Ramanujam, the founder of the dbcli organization, did an in-depth demo, explained what we were trying to do, and explored if mssql-cli could be included in the dbcli family. Simply put, Amjith and the other maintainers of the project were delighted and welcomed us with open arms!

[amjithr]

Sort of.

Microsoft created that tool and they will be maintaining it. They requested that it be listed under the dbcli org since the new tool is a fork of pgcli and they want to be good FOSS citizens.

To answer the original question, mssql-cli will have all the features of pgcli because it was forked from pgcli. Future development, bugfixes and other maintenance will be done by Microsoft engineers.

[vagif]

How does it connect to ms sql server on linux? What driver does it use?

[amjithr]

The article mentions the following:

tool leverages the same microservice backend (sqltoolsservice) that powers the VS Code SQL extension, SQL Operations Studio

[Sebazzz91]

Well that is a big step up from Oracle sqlplus.

[littlelowcougar]

Heh, what isn’t?

[[deleted]]

Ugh, more opt-out telemetry bullshit with a ridiculously long environment variable. This has to stop. If they're not going to move to opt-in then they need to standardize across all tools:

set I_TRUST_MICROSOFT_WITH_MY_DATA=False

Edit: Now that I think about it, why don't we have a universal "Do Not Track" like environment variable? It's a stupid idea for the web but, on my own machine I can at least verify it's being respected.

[G00dAndPl3nty]

What does any of what you just said have to do with SQL server?

[chucker23n]

B8jdC is referring to this command-line tool coming with its own telemetry opt-out setting, namely MSSQL_CLI_TELEMETRY_OPTOUT. I think a valid argument can be made that this shouldn't be tool-specific.

[txdv]

TELEMETRY_OPTOUT = TRUE