Skip to content

Commit ce39c11

Browse files
rothjarothja
committed
Fixing relative link to include file so images work
1 parent 580e960 commit ce39c11

55 files changed

Lines changed: 100 additions & 100 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/includes/tsql-appliesto-sslinux-only.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
<Token>**THIS TOPIC APPLIES TO:** ![no](./media/no.png)SQL Server on Windows ![yes](./media/yes.png)SQL Server on Linux ![no](./media/no.png)Azure SQL Database ![no](./media/no.png)Azure SQL Data Warehouse ![no](./media/no.png)Parallel Data Warehouse </Token>
1+
<Token>**THIS TOPIC APPLIES TO:** ![no](media/no.png)SQL Server on Windows![yes](media/yes.png)SQL Server on Linux![no](media/no.png)Azure SQL Database![no](media/no.png)Azure SQL Data Warehouse![no](media/no.png)Parallel Data Warehouse </Token>

‎docs/linux/quickstart-install-connect-docker.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.assetid: 82737f18-f5d6-4dce-a255-688889fdde69
1212
---
1313
# Run the SQL Server 2017 container image with Docker
1414

15-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
15+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1616

1717
In this quick start tutorial, you use Docker to pull and run the SQL Server 2017 RC2 container image, [mssql-server-linux](https://hub.docker.com/r/microsoft/mssql-server-linux/). Then connect with **sqlcmd** to create your first database and run queries.
1818

‎docs/linux/quickstart-install-connect-red-hat.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.assetid: 92503f59-96dc-4f6a-b1b0-d135c43e935e
1212
---
1313
# Install SQL Server and create a database on Red Hat
1414

15-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
15+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1616

1717
In this quick start tutorial, you first install SQL Server 2017 RC2 on Red Hat Enterprise Linux (RHEL) 7.3. Then connect with **sqlcmd** to create your first database and run queries.
1818

‎docs/linux/quickstart-install-connect-suse.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.assetid: 31ddfb80-f75c-4f51-8540-de6213cb68b8
1212
---
1313
# Install SQL Server and create a database on SUSE Linux Enterprise Server
1414

15-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
15+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1616

1717
In this quick start tutorial, you first install SQL Server 2017 RC2 on SUSE Linux Enterprise Server (SLES) v12 SP2. Then connect with **sqlcmd** to create your first database and run queries.
1818

‎docs/linux/quickstart-install-connect-ubuntu.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.assetid: 31c8c92e-12fe-4728-9b95-4bc028250d85
1212
---
1313
# Install SQL Server and create a database on Ubuntu
1414

15-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
15+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1616

1717
In this quick start tutorial, you first install SQL Server 2017 RC2 on Ubuntu 16.04. Then connect with **sqlcmd** to create your first database and run queries.
1818

‎docs/linux/sample-unattended-install-redhat.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.technology: database-engine
1111
---
1212
# Sample: Unattended SQL Server installation script for Red Hat Enterprise Linux
1313

14-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
14+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1515

1616
This sample Bash script installs SQL Server 2017 RC2 on Red Hat Enterprise Linux (RHEL) without interactive input. It provides examples of installing the database engine, the SQL Server command-line tools, SQL Server Agent, and performs post-install steps. You can optionally install full-text search and create an administrative user.
1717

‎docs/linux/sample-unattended-install-suse.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.technology: database-engine
1111
---
1212
# Sample: Unattended SQL Server installation script for SUSE Linux Enterprise Server
1313

14-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
14+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1515

1616
This sample Bash script installs SQL Server 2017 RC2 on SUSE Linux Enterprise Server (SLES) v12 SP2 without interactive input. It provides examples of installing the database engine, the SQL Server command-line tools, SQL Server Agent, and performs post-install steps. You can optionally install full-text search and create an administrative user.
1717

‎docs/linux/sample-unattended-install-ubuntu.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.technology: database-engine
1111
---
1212
# Sample: Unattended SQL Server installation script for Ubuntu
1313

14-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
14+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1515

1616
This sample Bash script installs SQL Server 2017 RC2 on Ubuntu 16.04 without interactive input. It provides examples of installing the database engine, the SQL Server command-line tools, SQL Server Agent, and performs post-install steps. You can optionally install full-text search and create an administrative user.
1717

‎docs/linux/sql-server-linux-active-directory-authentication.md‎

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -13,33 +13,33 @@ helpviewer_keywords:
1313
---
1414
# Active Directory Authentication with SQL Server on Linux
1515

16-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
16+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1717

18-
This document explains how to configure [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] on Linux to support Active Directory (AD) authentication, also known as integrated authentication. AD Authentication enables domain-joined clients on either Windows or Linux to authenticate to [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] using their domain credentials and the Kerberos protocol.
18+
This document explains how to configure [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] on Linux to support Active Directory (AD) authentication, also known as integrated authentication. AD Authentication enables domain-joined clients on either Windows or Linux to authenticate to [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] using their domain credentials and the Kerberos protocol.
1919

20-
AD Authentication has the following advantages over [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] Authentication:
20+
AD Authentication has the following advantages over [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Authentication:
2121

2222
* Users authenticate via single sign-on, without being prompted for a password.
23-
* By creating logins for AD groups, you can manage access and permissions in [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] using AD group memberships.
24-
* Each user has a single identity across your organization, so you don’t have to keep track of which [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] logins correspond to which people.
23+
* By creating logins for AD groups, you can manage access and permissions in [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] using AD group memberships.
24+
* Each user has a single identity across your organization, so you don’t have to keep track of which [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] logins correspond to which people.
2525
* AD enables you to enforce a centralized password policy across your organization.
2626

2727
## Prerequisites
2828

2929
Before you configure AD Authentication, you need to:
3030

3131
* Set up an AD Domain Controller (Windows) on your network
32-
* Install [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)]
32+
* Install [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]
3333
* [Red Hat Enterprise Linux](quickstart-install-connect-red-hat.md)
3434
* [SUSE Linux Enterprise Server](quickstart-install-connect-suse.md)
3535
* [Ubuntu](quickstart-install-connect-ubuntu.md)
3636

3737
> [!IMPORTANT]
3838
> At this time, the only authentication method supported for database mirroring endpoint is CERTIFICATE. WINDOWS authentication method will be enabled in a future release.
3939
40-
## Step 1: Join [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] host to AD domain
40+
## Step 1: Join [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] host to AD domain
4141

42-
Numerous tools exist to help you join the [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] host machine to your AD domain. This walkthrough uses **[realmd](https://www.freedesktop.org/software/realmd/docs/guide-active-directory-join.html)**, a popular open source package. If you haven't already, install both the realmd and Kerberos client packages on the [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] host machine using your Linux distribution's package manager:
42+
Numerous tools exist to help you join the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] host machine to your AD domain. This walkthrough uses **[realmd](https://www.freedesktop.org/software/realmd/docs/guide-active-directory-join.html)**, a popular open source package. If you haven't already, install both the realmd and Kerberos client packages on the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] host machine using your Linux distribution's package manager:
4343

4444
```bash
4545
# RHEL
@@ -57,13 +57,13 @@ If the Kerberos client package installation prompts you for a realm name, enter
5757
> [!NOTE]
5858
> This walkthrough uses "contoso.com" and "CONTOSO.COM" as example domain and realm names, respectively. You should replace these with your own values. These commands are case-sensitive, so make sure you use uppercase wherever it is used in this walkthrough.
5959
60-
Run the following command to verify that the [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] host machine is configured to use the AD domain controller for as a DNS nameserver:
60+
Run the following command to verify that the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] host machine is configured to use the AD domain controller for as a DNS nameserver:
6161

6262
```bash
6363
sudo realm discover contoso.com -v
6464
```
6565

66-
If your domain is not found, you need to configure your [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] host machine to use your AD domain controller's IP address as a DNS nameserver. The specific steps to do this depend on your network device configuration, domain configuration, and Linux distribution. Here are some example approaches.
66+
If your domain is not found, you need to configure your [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] host machine to use your AD domain controller's IP address as a DNS nameserver. The specific steps to do this depend on your network device configuration, domain configuration, and Linux distribution. Here are some example approaches.
6767

6868
### Example DNS configuration: Ubuntu
6969

@@ -156,7 +156,7 @@ Default principal: user@CONTOSO.COM
156156
157157
For more information, see the Red Hat documentation for [Discovering and Joining Identity Domains](https://access.redhat.com/documentation/Red_Hat_Enterprise_Linux/7/html/Windows_Integration_Guide/realmd-domain.html).
158158

159-
## Step 2: Create AD user for [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] and set SPN
159+
## Step 2: Create AD user for [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] and set SPN
160160

161161
> [!NOTE]
162162
> In the next steps we will use your [fully qualified domain name](https://en.wikipedia.org/wiki/Fully_qualified_domain_name). If you are on **Azure**, you will have to **[create one](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/portal-create-fqdn)** before you proceed.
@@ -172,7 +172,7 @@ New-ADUser mssql -AccountPassword (Read-Host -AsSecureString "Enter Password") -
172172
> [!NOTE]
173173
> It is a security best practice to have a dedicated AD account for SQL Server, so that SQL Server's credentials aren't shared with other services using the same account. However, you can reuse an existing AD account if you prefer, if you know the account's password (required to generate a keytab file in the next step).
174174
175-
Now set the ServicePrincipalName (SPN) for this account using the `setspn.exe` tool. The SPN must be formatted exactly as specified in the following example: You can find the fully qualified domain name of the [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] host machine by running `hostname --all-fqdns` on the [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] host, and the TCP port should be 1433 unless you have configured [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] to use a different port number.
175+
Now set the ServicePrincipalName (SPN) for this account using the `setspn.exe` tool. The SPN must be formatted exactly as specified in the following example: You can find the fully qualified domain name of the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] host machine by running `hostname --all-fqdns` on the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] host, and the TCP port should be 1433 unless you have configured [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] to use a different port number.
176176

177177
```PowerShell
178178
setspn -A MSSQLSvc/**<fully qualified domain name of host machine>**:**<tcp port>** mssql
@@ -185,9 +185,9 @@ setspn -A MSSQLSvc/**<fully qualified domain name of host machine>**:**<tcp port
185185
186186
For more information, see [Register a Service Principal Name for Kerberos Connections](../database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections.md).
187187

188-
## Step 3: Configure [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] service keytab
188+
## Step 3: Configure [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] service keytab
189189

190-
First, check the Key Version Number (kvno) for the AD account created in the previous step. Usually it will be 2, but it could be another integer if you changed the account's password multiple times. On the [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] host machine, run the following:
190+
First, check the Key Version Number (kvno) for the AD account created in the previous step. Usually it will be 2, but it could be another integer if you changed the account's password multiple times. On the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] host machine, run the following:
191191

192192
```bash
193193
kinit user@CONTOSO.COM
@@ -212,14 +212,14 @@ quit
212212
> [!NOTE]
213213
> The ktutil tool does not validate the password, so make sure you enter it correctly.
214214
215-
Anyone with access to this `keytab` file can impersonate [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] on the domain, so make sure you restrict access to the file such that only the `mssql` account has read access:
215+
Anyone with access to this `keytab` file can impersonate [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] on the domain, so make sure you restrict access to the file such that only the `mssql` account has read access:
216216

217217
```bash
218218
sudo chown mssql:mssql /var/opt/mssql/secrets/mssql.keytab
219219
sudo chmod 400 /var/opt/mssql/secrets/mssql.keytab
220220
```
221221

222-
Next, configure [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] to use this `keytab` file for Kerberos authentication:
222+
Next, configure [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] to use this `keytab` file for Kerberos authentication:
223223

224224
```bash
225225
sudo /opt/mssql/bin/mssql-conf set network.kerberoskeytabfile /var/opt/mssql/secrets/mssql.keytab
@@ -228,7 +228,7 @@ sudo systemctl restart mssql-server
228228

229229
## Step 4: Create AD-based logins in Transact-SQL
230230

231-
Connect to [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] and create a new, AD-based login:
231+
Connect to [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] and create a new, AD-based login:
232232

233233
```sql
234234
CREATE LOGIN [CONTOSO\user] FROM WINDOWS;
@@ -240,9 +240,9 @@ Verify that the login is now listed in the [sys.server_principals](../relational
240240
SELECT name FROM sys.server_principals;
241241
```
242242

243-
## Step 5: Connect to [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] using AD Authentication
243+
## Step 5: Connect to [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] using AD Authentication
244244

245-
Log in to a client machine using your domain credentials. Now you can connect to [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] without reentering your password, by using AD Authentication. If you create a login for an AD group, any AD user who is a member of that group can connect in the same way.
245+
Log in to a client machine using your domain credentials. Now you can connect to [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] without reentering your password, by using AD Authentication. If you create a login for an AD group, any AD user who is a member of that group can connect in the same way.
246246

247247
The specific connection string parameter for clients to use AD Authentication depends on which driver you are using. A few examples are below.
248248

@@ -264,7 +264,7 @@ sqlcmd -S mssql.contoso.com
264264

265265
### Example 2: SSMS on a domain-joined Windows client
266266

267-
Log in to a domain-joined Windows client using your domain credentials. Make sure [!INCLUDE[ssmanstudiofull-md](../../docs/includes/ssmanstudiofull-md.md)] is installed, then connect to your [!INCLUDE[ssNoVersion](../../docs/includes/ssnoversion-md.md)] instance by specifying **Windows Authentication** in the **Connect to Server** dialog.
267+
Log in to a domain-joined Windows client using your domain credentials. Make sure [!INCLUDE[ssmanstudiofull-md](../includes/ssmanstudiofull-md.md)] is installed, then connect to your [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] instance by specifying **Windows Authentication** in the **Connect to Server** dialog.
268268

269269
### AD Authentication using other client drivers
270270

‎docs/linux/sql-server-linux-availability-group-cluster-rhel.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.assetid: b7102919-878b-4c08-a8c3-8500b7b42397
1212
---
1313
# Configure RHEL Cluster for SQL Server Availability Group
1414

15-
[!INCLUDE[tsql-appliesto-sslinux-only](../../docs/includes/tsql-appliesto-sslinux-only.md)]
15+
[!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
1616

1717
This document explains how to create a three-node availability group cluster for SQL Server on Red Hat Enterprise Linux. For high availability, an availability group on Linux requires three nodes - see [High availability and data protection for availability group configurations](sql-server-linux-availability-group-ha.md). The clustering layer is based on Red Hat Enterprise Linux (RHEL) [HA add-on](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/pdf/High_Availability_Add-On_Overview/Red_Hat_Enterprise_Linux-6-High_Availability_Add-On_Overview-en-US.pdf) built on top of [Pacemaker](http://clusterlabs.org/).
1818

0 commit comments

Comments
 (0)