4 ms·
Not having to run Windows is a big factor. (Just so you know: I run a lot of Windows servers, so I'm not being knee-jerk snarky. This is a real cost).
by kabdib 10y ago
Not having to run Windows is a big factor. (Just so you know: I run a lot of Windows servers, so I'm not being knee-jerk snarky. This is a real cost).
- teilo 10y agoYes, and the cost savings go well beyond a Windows license + SA. Being able to leverage an existing toolchain for configuration management and deployment is a huge cost savings, given that the Windows alternatives are both expensive, more difficult to use, and break a lot more (IMHO).
- Scuds 10y agoapt install mssql-server https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-ubuntu https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-... and for the people doing docker https://hub.docker.com/r/microsoft/mssql-server-linux/ https://hub.docker.com/r/microsoft/mssql-server-linux/
- teilo 10y agoI was thinking more of Ansible, but yeah. I've done SQL Server installs on Windows Core, and it is painful. Aside from the obscure PowerShell commands, you have to write a config file - just to get the damn thing installed. Rubbish. (I hear it's gotten better in 2016 though).
- keithnz 10y agousually sql server dwarfs the costs of windows though?
- joosters 10y agoIt's not just the financial costs...
- keithnz 10y agomy experience of running sql server on windows is basically it is reasonably painless. about the most annoying thing about running windows is updates as they mostly want to restart the box. If you delay your updates, it can take 40 + minutes to restart once you decide to install them
- douche 10y agoThe only issue I've ever had with MSSQL is that the Express version comes configured out-of-the-box with a set of defaults that make it nearly useless. TCP/IP connections are turned off, and you have to go through and set all the protocols to use the normal SQL port.
- wolrah 10y agoI've seen SQL Express used basically like SQLite a number of times, where it's only being accessed by a local installation of something. Also if you're installing it manually (and thus having to configure it manually) the odds are good that you're a developer in which case it'll also only be accessed locally. It's a sane default to not listen to the network. A lot of users won't need it. Those that do can enable it. The port thing is handled automatically when you have your network clients working correctly. For the record I'm a SQLite/Postgres guy, the only reason I even know about the port thing is having to help a customer troubleshoot some software that uses SQL express a few weeks ago. Definitely not a MS defender normally, but your complaints are really silly.
- rbanffy 10y agoIt remains to be seen whether SQL Server on Linux will require less care and feeding than on Windows.
- snuxoll 10y agoBeing able to yum/apt-get install and edit a config file or run a couple quick commands is a lot easier than needing to figure out how to feed SETUP.EXE the right arguments and deal with a mess of arcane windows CLI tools + a mix of PowerShell to configure SQL Server. Automating the installation of PostgreSQL on Linux with ansible is a couple lines of tasks in a playbook + a template for postgresql.conf and pg_hba.conf. Automating the installation of SQL Server on Windows (as well as the installation of Windows in general if you aren't using System Center) is a huge pain in the ass. That's enough less "care and feeding" for me.