Unable to get MS SQL Operations Studio working

mfoley · 08-25-2018, 10:11 PM

I've recently installed MS SQL Server Express 2017 on Slackware64 14.2. I can do queries from the command line using /opt/mssql-tools/bin/sqlcmd. I can also do queries from a remote host via port 1433. In KDE, I can run sqlops as a normal user. I get the SERVERS connection page. The stderr output seems innocuous:

Code:

$ sqlops
[main 4:18:01 PM] update#setState idle
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
[main 4:18:32 PM] update#setState checking for updates
[main 4:18:33 PM] update#setState idle

I've tried entering the local hostname, hostname/SQLEXPRESS, and the hostname of a remote server to which I'm able to connect from java on other Linux hosts. All I get is a spinning indicator and it never connects or gives any sort of error. No errors logged to /var/opt/mssql/log/errorlog.

If I try

Code:

sqlcmd -U sa -P password -S labrat\\SQLExpress

I get "Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : MAX_PROVS: Error Locating Server/Instance Specified [xFFFFFFFF]. ... Check if instance name is correct and if SQL Server is configured to allow remote connections."

Any ideas?

Habitual · 08-26-2018, 10:14 AM

Quote:

Originally Posted by mfoley

Check if instance name is correct and if SQL Server is configured to allow remote connections."

Any ideas?

One or two

Code:

telnet labrat 1433

what happens?

Study https://blogs.msdn.microsoft.com/sql...nce-specified/

mfoley · 08-27-2018, 12:37 PM

Quote:

Originally Posted by Habitual

One or two

Code:

telnet labrat 1433

what happens?

Study https://blogs.msdn.microsoft.com/sql...nce-specified/

telnet labrat 1433 works. Not only that, I can do queries from a remote host to this SQL Server host via port 1433 and it works.

As far as the instance name goes, I've no idea how to find that and I've been searching quite extensively. All of the methods I've found for this are how to determine the instance name on a Windows hosted SQL Server and they involve examining the registry or running a Power Shell script. None of which helps for a Linux hosted SQL Server. Based on what I've read, the default instance name is SQLEXPRESS. I've also tried labrat\MSSQLSERVER

Something I didn't notice before, when I start sqlops I get the message "Failed to start sql-tools service". It flashed up briefly then goes away. Perhaps there is some service that needs to be running for sqlops to work? I'll check into that.

Habitual · 09-01-2018, 01:17 PM

Quote:

Originally Posted by mfoley

Based on what I've read, the default instance name is SQLEXPRESS. I've also tried labrat\MSSQLSERVER

try:

Code:

sqlcmd -U sa -P password -S labrat

see what happens.