The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Lots of you will now say that you already knew that, since you have it as a VM in Azure.
There was some error on not being able to install "mssql-tools" due to a missing dependency. Apt-get that dependency, get a similar message on a new package. Try that, another dependency. After four of those, a Y/n on install, and work your way up through the dependencies. That's the tools (like SqlCmd), Sql Server was already running.
Connection error; so this idiot tried to connect using Windows Authentication
Try Sql Server authentication and login with sa, new connection error. Quick google teaches me that SqlWb needs to have the (default) port number after the instance name. So, add ",1433" after the instance name, and it connects, acting like a normal Sql Server instance would.
Created a database, created a table, from MS Sql Wb running on a Win10 machine. No additional errors, which must mean I done something wrong. Reboot, and it still works! It's running on not-so-great hardware (hence Linux), but it is still bloody fast (not much other stuff installed). If it works on that machine, then it may work on my Raspberry. Imagine a backup-databaseserver the size of a creditcard. Now all I need to build my own cloud[^] is to get RAID5 working on cheap USB pendrives.
Thank you Microsoft (and Scott)
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Ofcourse, since there's only so much ports on a system and running them all behind a single hub defeats the purpose of the excercise a bit. Still, I'm not the only one with that idea, and it seems it works for some people;