Setting up SQL Server High-Availability between Windows and Linux with SQL Server 2017

Play Setting up SQL Server High-Availability between Windows and Linux with SQL Server 2017
Sign in to queue


Tobias and Slava are back in the studio in this awesome video to show high-availability with SQL Server 2017 between Windows and Linux. After spending a few minutes discussing the background, thought process, discussions that went on trying to determine if this was even possible, and the applicable scenarios, Tobias jumps right into the demo [06:20] to show that yes, Virginia, it is possible, and that it is quite easy to create and configure Availability Groups on both Windows and Linux. 

As always, we have a lot of fun, and this is definitely an episode you don't want to miss!

Be sure to follow the Data Exposed show on Twitter at @DataExposed!



The Discussion

  • User profile image


  • User profile image

    Is it possible to have not only the video, but also all the T-SQL scripts used? Is there perhaps a Power Point file or some othe source, people can use and save time for copying the commands from the screen ?

  • User profile image
  • User profile image

    @TobiasT: Great walk through Tobias and Slava.  Tobias, could you also place your sudo scripts in github and any highlight any prerequisite steps required e.g. hosts file, firewall config etc.

  • User profile image

    I understand building AlwaysOn, but do you have a video on Failover settings using Pacemaker?
    This is three Linux environments.

  • User profile image
    Ysaias Portes

    Hi @TobiasT
    I am getting an error: Apparently AUTOMATIC SEEDING is not working for me...I am not sure what I missed, but getting a typical restore error in Error Log.

    Automatic seeding of availability database 'test' in availability group 'MyAGDistr' failed with a transient error. The operation will be retried.
    The operating system returned the error '3(The system cannot find the path specified.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on '\var\opt\mssql\data\test.ldf'.
    File 'test_log' cannot be restored to '\var\opt\mssql\data\test.ldf'. Use WITH MOVE to identify a valid location for the file

  • User profile image

    Hello, Thank You for the nice stuff. its very helpful

Add Your 2 Cents