You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -79,6 +79,7 @@ The following steps increase the memory for Docker for Windows to 4 GB.
79
79
|-----|-----|
80
80
|**-e 'ACCEPT_EULA=Y'**| Set the **ACCEPT_EULA** variable to any value to confirm your acceptance of the [End-User Licensing Agreement](http://go.microsoft.com/fwlink/?LinkId=746388). Required setting for the SQL Server image. |
81
81
|**-e 'SA_PASSWORD=\<YourStrong!Passw0rd\>'**| Specify your own strong password that is at least 8 characters and meets [SQL Server's password requirements](../relational-databases/security/password-policy.md). Required setting for the SQL Server image. |
82
+
| **-e 'MSSQL_PID=Developer'** | Specifies the edition or product key. In this example, the freely licensed Developer Edition is used for non-production testing. For other values, see [Configure SQL Server settings with environment variables on Linux](sql-server-linux-configure-environment-variables.md). |
82
83
| **-p 1401:1433** | Map a TCP port on the host environment (first value) with a TCP port in the container (second value). In this example, SQL Server is listening on TCP 1433 in the container and this is exposed to the port, 1401, on the host. |
83
84
| **microsoft/mssql-server-linux** | The SQL Server Linux container image. Unless otherwise specified, this defaults to the **latest** image. |
84
85
@@ -100,7 +101,7 @@ The SA account is a system administrator on the SQL Server instance that gets cr
100
101
101
102
1. Choose a strong password to use for the SA user.
102
103
103
-
1. Use `docker exec` to run **sqlcmd** to change the password using Transact-SQL.
104
+
1. Use `docker exec` to run **sqlcmd** to change the password using Transact-SQL. Replace `<Old Password>` and `<New Password>` with your password values.
104
105
105
106
> ```bash
106
107
> docker exec -it <Container ID> /opt/mssql-tools/bin/sqlcmd -S localhost -U SA -P '<Old Password>' -Q 'ALTER LOGIN SA WITH PASSWORD="<New Password>";'
Copy file name to clipboardExpand all lines: docs/linux/sql-server-linux-configure-environment-variables.md
+44-11Lines changed: 44 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ description: This topic describes how to use environment variables to configure
6
6
author: rothja
7
7
ms.author: jroth
8
8
manager: jhubbard
9
-
ms.date: 05/22/2017
9
+
ms.date: 07/17/2017
10
10
ms.topic: article
11
11
ms.prod: sql-linux
12
12
ms.technology: database-engine
@@ -25,31 +25,64 @@ ms.assetid:
25
25
---
26
26
# Configure SQL Server settings with environment variables on Linux
27
27
28
-
You can use several different environment variables to configure SQL Server 2017 RC1 on Linux. This topic provides a list of the settings that are configurable using environment variables.
28
+
You can use several different environment variables to configure SQL Server 2017 RC1 on Linux. These variables are used in two scenarios:
29
29
30
-
> [!IMPORTANT]
31
-
> At this time, the environment variables only configure [SQL Server running in Docker](sql-server-linux-setup-docker.md). To configure the SQL Server service outside of a Docker scenario, see [Configure SQL Server on Linux with the mssql-conf tool](sql-server-linux-configure-mssql-conf.md).
30
+
- Initial unprompted setup with `mssql-conf -n setup` command.
31
+
- Configuring a new [SQL Server container in Docker](quickstart-install-connect-docker.md).
32
+
33
+
> [!TIP]
34
+
> If you need to configure SQL Server after these setup scenarios, see [Configure SQL Server on Linux with the mssql-conf tool](sql-server-linux-configure-mssql-conf.md).
32
35
33
36
## Environment variables
34
37
35
38
| Environment variable | Description |
36
39
|-----|-----|
37
-
|**ACCEPT_EULA**| Accept the SQL Server license agreement when set to any value (for example, 'Y'). Used on first install only. |
38
-
|**SA_PASSWORD**| Configure the SA user password. Used on first install only. |
40
+
|**ACCEPT_EULA**| Accept the SQL Server license agreement when set to any value (for example, 'Y'). |
41
+
|**SA_PASSWORD**| Configure the SA user password. |
42
+
|**MSSQL_PID**| Set the SQL Server edition or product key. Possible values include: Evaluation, Developer, Express, Web, Standard, Enterprise, or a product key in the form of #####-#####-#####-#####-#####, where '#' is a number or a letter. |
43
+
|**MSSQL_LCID**| Sets the language ID to use for SQL Server. For example 1036 is French. |
44
+
|**MSSQL_COLLATION**| Sets the default collation for SQL Server. This overrides the default mapping of language id (LCID) to collation. |
45
+
|**MSSQL_MEMORY_LIMIT_MB**| Sets the maximum amount of memory SQL Server can use. By default it is 80% of the total physical memory. |
39
46
|**MSSQL_TCP_PORT**| Configure the TCP port that SQL Server listens on (default 1433). |
40
47
|**MSSQL_IP_ADDRESS**| Set the IP address. Currently, the IP address must be IPv4 style (0.0.0.0). |
41
-
|**MSSQL_BACKUP_DIR**|Sets the Default backup directory location. |
48
+
|**MSSQL_BACKUP_DIR**|Set the Default backup directory location. |
42
49
|**MSSQL_DATA_DIR**| Change the directory where the new SQL Server database data files (.mdf) are created. |
43
-
|**MSSQL_LOG_DIR**|Changes the directory where the new SQL Server database log (.ldf) files are created. |
50
+
|**MSSQL_LOG_DIR**|Change the directory where the new SQL Server database log (.ldf) files are created. |
44
51
|**MSSQL_DUMP_DIR**| Change the directory where SQL Server will deposit the memory dumps and other troubleshooting files by default. |
The following example runs **mssql-conf setup** without prompts (`-n`). This mode looks for environment variables to use for configuration. The following environment variables are specified:
57
+
58
+
-**ACCEPT_EULA** accepts the end user license agreement.
59
+
-**MSSSQL_PID** specifies the freely licensed Developer Edition of SQL Server for non-production use.
60
+
-**SA_PASSWORD** sets a strong password.
61
+
-**MSSQL_TCP_PORT** sets the TCP port that SQL Server listens on to 1234.
The following example docker command uses the following environment variables to create a new SQL Server 2017 container:
70
+
71
+
-**ACCEPT_EULA** accepts the end user license agreement.
72
+
-**MSSSQL_PID** specifies the freely licensed Developer Edition of SQL Server for non-production use.
73
+
-**SA_PASSWORD** sets a strong password.
74
+
-**MSSQL_TCP_PORT** sets the TCP port that SQL Server listens on to 1234. This means that instead of mapping port 1433 (default) to a host port, the custom TCP port must be mapped with the `-p 1234:1234` command in this example.
75
+
76
+
If you are running Docker on Linux/macOS, use the following syntax with single quotes:
The following docker run command uses **MSSQL_TCP_PORT** to set the TCP port that SQL Server listens on. In this case, the host port mapping must that this new port into consideration. Instead of mapping port 1433 (default) to a host port, the custom TCP port must be mapped (1234 in this example).
82
+
If you are running Docker on Windows, use the following syntax with double quotes:
Copy file name to clipboardExpand all lines: docs/linux/sql-server-linux-migrate-overview.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,8 +41,7 @@ For a tutorial on migrating a database with backup and restore, see the followin
41
41
42
42
It is also possible to export your database to a BACPAC file (a compressed file that contains your database schema and data). If you have a BACPAC file, you can transfer this file to your Linux machine and then import it to SQL Server. For more information, see the following topics:
43
43
44
-
-[Export and import a database with sqlpackage](sql-server-linux-migrate-sqlpackage.md)
45
-
-[Export and import a database with SSMS](sql-server-linux-migrate-ssms.md)
44
+
-[Export and import a database with SSMS or SqlPackage.exe](sql-server-linux-migrate-ssms.md)
46
45
47
46
## Migrate from other database servers
48
47
You can migrate databases on other database systems to SQL Server 2017 on Linux. This includes Microsoft Access, DB2, MySQL, Oracle, and Sybase databases. In this scenario, use the SQL Server Management Assistant (SSMA) to automate the migration to SQL Server on Linux. For more information, see [Use SSMA to migrate databases to SQL Server on Linux](sql-server-linux-migrate-ssma.md).
# Export and import a database on Linux with SQL Server Management Studio on Windows
26
+
# Export and import a database on Linux with SSMS or SqlPackage.exe on Windows
27
27
28
-
This topic shows how to use [SQL Server Management Studio (SSMS)](https://msdn.microsoft.com/library/mt238290.aspx) to export and import a database on SQL Server 2017 RC1 on Linux. SSMS is a Windows application, so use SSMS when you have a Windows machine that can connect to a remote SQL Server instance on Linux.
28
+
This topic shows how to use [SQL Server Management Studio (SSMS)](https://msdn.microsoft.com/library/mt238290.aspx)and [SqlPackage.exe](https://msdn.microsoft.com/library/hh550080.aspx)to export and import a database on SQL Server 2017 RC1 on Linux. SSMS and SqlPackage.exe are Windows applications, so use this technique when you have a Windows machine that can connect to a remote SQL Server instance on Linux.
29
29
30
30
You should always install and use the most recent version of SQL Server Management Studio (SSMS) as described in [Use SSMS on Windows to connect to SQL Server on Linux](sql-server-linux-develop-use-ssms.md)
31
31
@@ -68,5 +68,22 @@ The *.BACPAC file is successfully created at the location you chose and you are
68
68
69
69
The *.BACPAC file is imported to create a new database in the target server you specified.
It is also possible to use the SQL Server Data Tools (SSDT) command-line tool, [SqlPackage.exe](https://msdn.microsoft.com/library/hh550080.aspx) to export and import BACPAC files.
74
+
75
+
The following example command exports a BACPAC file:
Copy file name to clipboardExpand all lines: docs/linux/sql-server-linux-release-notes.md
-7Lines changed: 0 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,13 +144,6 @@ The following sections describe known issues with this release of SQL Server 201
144
144
#### Full-Text Search
145
145
- Not all filters are available with this release, including filters for Office documents. For a list of supported filters, see [Install SQL Server Full-Text Search on Linux](sql-server-linux-setup-full-text-search.md#filters).
146
146
147
-
#### SqlPackage
148
-
- Using SqlPackage requires specifying an absolute path for files. Using relative paths will map the files under the "/tmp/sqlpackage.\<code\>/system/system32" folder.
149
-
150
-
-**Resolution**: Use absolute file paths.
151
-
152
-
- SqlPackage shows the location of files with a "C:\\" prefix.
153
-
154
147
#### SQL Server Integration Services (SSIS)
155
148
You can run SSIS packages on Linux. For more info, see the [blog post announcing SSIS support for Linux](https://blogs.msdn.microsoft.com/ssis/2017/05/17/ssis-helsinki-is-available-in-sql-server-vnext-ctp2-1/). Please note the following known issues with this release.
- Added environment variables for initial SQL Server setup. For more information, see [Configure SQL Server settings with environment variables on Linux](sql-server-linux-configure-environment-variables.md).
30
+
- Removed **sqlpackage** from installed binaries. SqlPackage can still be run against Linux remotely from Windows.
0 commit comments