Package Details: mssql-server 15.0.4083.2-1

Git Clone URL: (read-only, click to copy)
Package Base: mssql-server
Description: Microsoft SQL Server for Linux
Upstream URL:
Licenses: unknown
Submitter: flash2k2
Maintainer: doctorzeus
Last Packager: doctorzeus
Votes: 21
Popularity: 1.01
First Submitted: 2016-11-17 09:25
Last Updated: 2021-01-27 08:47

Latest Comments

1 2 3 4 5 Next › Last »

MrHritik commented on 2020-12-15 21:20

The upstream URL is invalid. Please fix.
EDIT: Fixed

too commented on 2020-10-07 08:12

@doctorzeus separate packages make perfect sense, I thought about doing one at least for lts myself, but learning the packaging spec is still on todo :) and a single maintainer for related packages would probably make more sense as well.

doctorzeus commented on 2020-10-07 03:18


I think it would be best introduced as a separate AUR package which would then depend on mssql-server.

I might be wrong but I'm pretty sure the AUR discourages bundling packages in this fashion to prevent mission creep etc..

too commented on 2020-10-05 09:15

To package authors - are you considering adding mssql feature packages in addition to the main pkg? I manually installed matching version mssql-server-fts from deb and it works fine but there is no aur package for it yet:

dpkg --extract ./mssql-server-fts_15.0.4053.23-2_amd64.deb /

Current list of available additional packages includes high availability, fts, extensibility, java extensibility and polybase:

ArthurBorsboom commented on 2020-03-10 12:48

systemd[1]: Configuration file /usr/lib/systemd/system/mssql-server.service is marked executable. Please remove executable permission bits. Proceeding anyway.

gabrielmldantas commented on 2020-02-03 14:11

@doctorzeus I never used SQLAgent so I don't really know what's going wrong. I followed these two tutorials ( and and it seems to work.

I updated the package because I discovered that Microsoft now specifies the Python 2 interpreter on the scripts, so the sed used to correct the interpreter was wrong.

doctorzeus commented on 2020-02-02 03:35

@gabrielmldantas Did a fresh install this weekend and still getting the same error unfortunately.

Did Microsoft remove SQLAgent availability from the Developer license as otherwise I can't find anything on google referencing the issue so assuming its a package/distro issue?

doctorzeus commented on 2020-01-09 01:40

@gabrielmldantas no luck unfortunately, guessing it's something todo with the upgrade from 2017-2019.. Going to try a fresh install..

Is Microsoft maintaining the 2017 one? If so someone could always start a separate package.

gabrielmldantas commented on 2020-01-08 12:36

@doctorzeus I didn't have this problem but the 2 or 3 last versions of SQL Server had a problem with OpenSSL causing connection failures. That's why I linked the correct OpenSSL libraries directly into the installation directory. Anyway, a new version was released yesterday and it seems to not need the link anymore, so I removed them from the PKGBUILD. You can try to update to see if it works for you.

doctorzeus commented on 2020-01-08 01:39

Don't know if this is package specific (will delete if I find its not) but since the update to 15.0.2000.5 sqlagent refuses to start with:

SQL Server does not accept the connection (error: 11001). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.

The agent makes several attempts and finally gives up with the error:

SQLServer Error: 11001, TCP Provider: No such host is known. [SQLSTATE 08001]

Might be to do with the upgrade from 2017 to 2019.