Greetings all. I thought I’d share a small victory and also inquire as to whether anyone else has targeted any production deployments of MSSQL Server on Linux w/ Ignition. I just tried it out today and it worked just fine!
One thing that I found was that I couldn’t use even the default instance name when connecting to my SQL instance on Linux. I had to omit it altogether:
This seems reasonable I suppose since I couldn’t find SQL Server Browser listening on UDP 1434 like it would be on a Windows box. There is 1433/tcp and 1434/tcp, but no 1434/udp, which based on the link here (http://sqlmag.com/sql-server/sql-server-tcp-and-udp-ports) suggests is the SQL Server Browser port used for named instances.
Below is the output of netstat -lntu on my linux machine:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:1433 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:1434 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:32000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:548 0.0.0.0:* LISTEN
tcp6 0 0 :::8043 :::* LISTEN
tcp6 0 0 127.0.0.1:45900 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::8088 :::* LISTEN
tcp6 0 0 :::8060 :::* LISTEN
tcp6 0 0 ::1:4700 :::* LISTEN
tcp6 0 0 :::4096 :::* LISTEN
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:33145 0.0.0.0:*
udp6 0 0 :::5353 :::*
udp6 0 0 :::58984 :::*
udp6 0 0 :::4445 :::*
udp6 0 0 :::55914 :::*
I’d be interested to hear any other folks interested in (or already) deploying SQL Server on Linux with Ignition. Exciting stuff!