SQL Server v.Next - Linux Installation Step by Step

  • Comments posted to this topic are about the item SQL Server v.Next - Linux Installation Step by Step

  • Thanks for the detailed article.

  • Very nice post!

    Just a consideration: there's no need to use "sudo" when you are connected as root. If logged as a non-root user, though, the redirections like

    sudo curl https://packages.microsoft.com/config/rhel/7/mssql-server.repo > /etc/yum.repos.d/mssql-server.repo

    won't work, because the redirection will be executed as the non-root user. You should use

    curl https://packages.microsoft.com/config/rhel/7/mssql-server.repo |sudo tee /etc/yum.repos.d/mssql-server.repo

    Thanks for the detailed howto!

  • Hi,

    sorry for my english (i'm italian), but i have a thought in my head and i need to share it with someone.

    Feel free to move this discussion if you think this is the wrong place to speak about this argument.

    I'm musing about the sense of this SQL Server porting.

    Assuming a reliable and common sensed SQL Server is expected to cover the task of database server and no more (no web server etc.), i can't see where is the gain in running at the top of Linux.

    I can see only one advantage: Linux is free (at least until you don't need a subscription like RedHat one).

    But we are speaking about a few hundred dollars of investments for the OS compared to the much higher SQL licensing costs.

    And, well, Microsoft would have saved a lot of investments for this development just giving for free a Windows Server corresponding license bundled with SQL Server.

    And what about the headaches?

    Nobody has already mentioned the compatibility between the two versions but i bet is not an easy street.

    For example, are we sure the SSIS packets developed for Windows version can run on Linux out-of-the-box?

    And what about the Oledb drivers? Sometimes are developed by 3rd parties and a porting is not granted.

    I think we are only putting ourseves in trouble for free.

  • Much thanks for the tutorial, great job

  • massimo.giacomello - Wednesday, December 28, 2016 9:30 AM

    Hi,sorry for my english (i'm italian), but i have a thought in my head and i need to share it with someone.Feel free to move this discussion if you think this is the wrong place to speak about this argument.I'm musing about the sense of this SQL Server porting.Assuming a reliable and common sensed SQL Server is expected to cover the task of database server and no more (no web server etc.), i can't see where is the gain in running at the top of Linux.I can see only one advantage: Linux is free (at least until you don't need a subscription like RedHat one).But we are speaking about a few hundred dollars of investments for the OS compared to the much higher SQL licensing costs.And, well, Microsoft would have saved a lot of investments for this development just giving for free a Windows Server corresponding license bundled with SQL Server.And what about the headaches?Nobody has already mentioned the compatibility between the two versions but i bet is not an easy street.For example, are we sure the SSIS packets developed for Windows version can run on Linux out-of-the-box? And what about the Oledb drivers? Sometimes are developed by 3rd parties and a porting is not granted.I think we are only putting ourseves in trouble for free.

    In my thinking another additional benefit would be entering the "black screen" market. Some DBAs who are used to linux and products like Oracle, used to typing commands rather than clicking buttons would love to tell their management that they can get a cheaper database to run on Linux for their small deployements. This opens a big market for Microsoft. I think they targett is not necessarily those who are on Windows and want to move to Linux but those who are on Linux and DO NOT like Windows.

    Br. Kenneth Igiri
    https://kennethigiri.com
    All nations come to my light, all kings to the brightness of my rising

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply