Skip to content

new-updated-linux.md

Latest commit

 

History

History
211 lines (112 loc) · 10.7 KB

new-updated-linux.md

File metadata and controls

211 lines (112 loc) · 10.7 KB
title Updated - SQL Server on Linux docs | Microsoft Docs
description Display snippets of updated content for recently changed in documentation, for Microsoft SQL Server on Linux.
manager craigg
author MightyPen
ms.author genemi
ms.topic article
ms.custom sql-linux,UpdArt.exe
ms.suite sql
ms.prod_service sql-non-specified
ms.component
ms.date 02/03/2018

New and Recently Updated: SQL Server on Linux docs

Nearly every day Microsoft updates some of its existing articles on its Docs.Microsoft.com documentation website. This article displays excerpts from recently updated articles. Links to new articles might also be listed.

This article is generated by a program that is rerun periodically. Occasionally an excerpt can appear with imperfect formatting, or as markdown from the source article. Images are never displayed here.

Recent updates are reported for the following date range and subject:

  • Date range of updates:   2017-12-03   -to-   2018-02-03
  • Subject area:   Microsoft SQL Server on Linux.

 

New Articles Created Recently

The following links jump to new articles that have been added recently.

  1. Configure multiple-subnet Always On Availability Groups and failover cluster instances
  2. Create and configure an availability group for SQL Server on Linux
  3. Deploy a Pacemaker cluster for SQL Server on Linux
  4. SQL Server on Linux Frequently Asked Questions (FAQ)
  5. SQL Server availability basics for Linux deployments
  6. Configure a SQL Server container in Kubernetes for high availability

 

Updated Articles with Excerpts

This section displays the excerpts of updates gathered from articles that have recently experienced a large update.

The excerpts displayed here appear separated from their proper semantic context. Also, sometimes an excerpt is separated from important markdown syntax that surrounds it in the actual article. Therefore these excerpts are for general guidance only. The excerpts only enable you to know whether your interests warrant taking the time to click and visit the actual article.

For these and other reasons, do not copy code from these excerpts, and do not take as exact truth any text excerpt. Instead, visit the actual article.

 

Compact List of Articles Updated Recently

This compact list provides links to all the updated articles that are listed in the Excerpts section.

  1. Always On Availability Groups on Linux
  2. Extract, transform, and load data on Linux with SSIS

 

 

1.   Always On Availability Groups on Linux

Updated: 2018-01-31           (Next)

 

Automatic failover of an AG is possible when the following conditions are met:

  • The primary and the secondary replica are set to synchronous data movement.
  • The secondary has a state of synchronized (not synchronizing), meaning the two are at the same data point.
  • The cluster type is set to External. Automatic failover is not possible with a cluster type of None.
  • The sequence_number of the secondary replica to become the primary has the highest sequence number – in other words, the secondary replica's sequence_number matches the one from the original primary replica.

If these conditions are met and the server hosting the primary replica fails, the AG will change ownership to a synchronous replica. The behavior for synchronous replicas (of which there can be three total: one primary and two secondary replicas) can further be controlled by required_synchronized_secondaries_to_commit. This works with AGs on both Windows and Linux, but is configured completely differently. On Linux, the value is configured automatically by the cluster on the AG resource itself.

Configuration-only replica and quorum

Also new in SQL Server 2017 as of CU1 is a configuration-only replica. Because Pacemaker is different than a WSFC, especially when it comes to quorum and requiring STONITH, having just a two-node configuration will not work when it comes to an AG. For an FCI, the quorum mechanisms provided by Pacemaker can be fine, because all FCI failover arbitration happens at the cluster layer. For an AG, arbitration under Linux happens in SQL Server, where all the metadata is stored. This is where the configuration-only replica comes into play.

Without anything else, a third node and at least one synchronized replica would be required. This would not work for SQL Server Standard, since it can only have two replicas participating in an AG. The configuration-only replica stores the AG configuration in the master database, same as the other replicas in the AG configuration. The configuration-only replica does not have the user databases participating in the AG. The configuration data is sent synchronously from the primary. This configuration data is then used during failovers, whether they are automatic or manual.

 

 

2.   Extract, transform, and load data on Linux with SSIS

Updated: 2018-01-31           (Previous)

 

```
SSIS_PACKAGE_DECRYPT=test /opt/ssis/bin/dtexec /f package.dtsx
```

  1. Specify the /de[crypt] option to enter the password interactively, as shown in the following example:

    /opt/ssis/bin/dtexec /f package.dtsx /de

Enter decryption password:

  2. Specify the /de option to provide the password on the command line, as shown in the following example. This method is not recommended because it stores the decryption password with the command in the command history.

    opt/ssis/bin/dtexec /f package.dtsx /de test

Warning: Using /De[crypt] <password> may store decryption password in command history.

You can use /De[crypt] instead to enter interactive mode,
or use environment variable SSIS_PACKAGE_DECRYPT to set decryption password.

Design packages

Connect to ODBC data sources. With SSIS on Linux CTP 2.1 Refresh and later, SSIS packages can use ODBC connections on Linux. This functionality has been tested with the SQL Server and the MySQL ODBC drivers, but is also expected to work with any Unicode ODBC driver that observes the ODBC specification. At design time, you can provide either a DSN or a connection string to connect to the ODBC data; you can also use Windows authentication. For more info, see the blog post announcing ODBC support on Linux.

Similar articles about new or updated articles

This section lists very similar articles for recently updated articles in other subject areas, within our public GitHub.com repository: MicrosoftDocs/sql-docs.

Subject areas that do have new or recently updated articles

Subject areas that do not have any new or recently updated articles