This tutorial is for Symantec Endpoint Protection Manager 12.1 Fresh Install - SQL Database. SQL SERVER – How to Install New Sample Database WideWorldImportersDW.bak December 26, 2017 Pinal Dave SQL Tips and Tricks 2 Comments Last year, I have written a blog to install sample database WideWorldImporters SQL SERVER 2016 – How to Import New Sample Database WideWorldImporters. SQL Tutorial 2 Installing MySQL Makinde Babatunde. Unsubscribe from Makinde Babatunde? How to Install & Configure printer, Network Printer - Duration: 36:05.
-->In this quickstart, you install SQL Server 2017 or SQL Server 2019 on Red Hat Enterprise Linux (RHEL). You then connect with sqlcmd to create your first database and run queries.
In this quickstart, you install SQL Server 2019 preview on Red Hat Enterprise Linux (RHEL) 7.3+. You then connect with sqlcmd to create your first database and run queries.
Tip
This tutorial requires user input and an internet connection. If you are interested in the unattended or offline installation procedures, see Installation guidance for SQL Server on Linux.
Prerequisites
You must have a RHEL 7.3, 7.4, 7.5, or 7.6 machine with at least 2 GB of memory.
To install Red Hat Enterprise Linux on your own machine, go to https://access.redhat.com/products/red-hat-enterprise-linux/evaluation. You can also create RHEL virtual machines in Azure. See Create and Manage Linux VMs with the Azure CLI, and use --image RHEL in the call to az vm create.
If you have previously installed a CTP or RC release of SQL Server 2017, you must first remove the old repository before following these steps. For more information, see Configure Linux repositories for SQL Server 2017 and 2019.
For other system requirements, see System requirements for SQL Server on Linux.
Install SQL Server
To configure SQL Server on RHEL, run the following commands in a terminal to install the mssql-server package:
Download the Microsoft SQL Server 2017 Red Hat repository configuration file:
Tip
If you want to try SQL Server 2019 , you must instead register the Preview (2019) repository. Use the following command for SQL Server 2019 installations:
Run the following commands to install SQL Server:
After the package installation finishes, run mssql-conf setup and follow the prompts to set the SA password and choose your edition.
Tip
The following SQL Server 2017 editions are freely licensed: Evaluation, Developer, and Express.
Note
Make sure to specify a strong password for the SA account (Minimum length 8 characters, including uppercase and lowercase letters, base 10 digits and/or non-alphanumeric symbols).
Once the configuration is done, verify that the service is running:
To allow remote connections, open the SQL Server port on the firewall on RHEL. The default SQL Server port is TCP 1433. If you are using FirewallD for your firewall, you can use the following commands:
At this point, SQL Server is running on your RHEL machine and is ready to use!
Install SQL Server
To configure SQL Server on RHEL, run the following commands in a terminal to install the mssql-server package:
Download the Microsoft SQL Server 2019 preview Red Hat repository configuration file:
Run the following commands to install SQL Server:
After the package installation finishes, run mssql-conf setup and follow the prompts to set the SA password and choose your edition.
Note
Make sure to specify a strong password for the SA account (Minimum length 8 characters, including uppercase and lowercase letters, base 10 digits and/or non-alphanumeric symbols).
Once the configuration is done, verify that the service is running:
To allow remote connections, open the SQL Server port on the firewall on RHEL. The default SQL Server port is TCP 1433. If you are using FirewallD for your firewall, you can use the following commands:
At this point, SQL Server 2019 preview is running on your RHEL machine and is ready to use!
Install the SQL Server command-line tools
To create a database, you need to connect with a tool that can run Transact-SQL statements on the SQL Server. The following steps install the SQL Server command-line tools: sqlcmd and bcp.
Download the Microsoft Red Hat repository configuration file.
If you had a previous version of mssql-tools installed, remove any older unixODBC packages.
Run the following commands to install mssql-tools with the unixODBC developer package.
For convenience, add
/opt/mssql-tools/bin/to your PATH environment variable. This enables you to run the tools without specifying the full path. Run the following commands to modify the PATH for both login sessions and interactive/non-login sessions:
Connect locally
The following steps use sqlcmd to locally connect to your new SQL Server instance.
Run sqlcmd with parameters for your SQL Server name (-S), the user name (-U), and the password (-P). In this tutorial, you are connecting locally, so the server name is
localhost. The user name isSAand the password is the one you provided for the SA account during setup.Tip
You can omit the password on the command line to be prompted to enter it.
Tip
If you later decide to connect remotely, specify the machine name or IP address for the -S parameter, and make sure port 1433 is open on your firewall.
If successful, you should get to a sqlcmd command prompt:
1>.If you get a connection failure, first attempt to diagnose the problem from the error message. Then review the connection troubleshooting recommendations.
Create and query data
The following sections walk you through using sqlcmd to create a new database, add data, and run a simple query.
Create a new database
The following steps create a new database named TestDB.
From the sqlcmd command prompt, paste the following Transact-SQL command to create a test database:
On the next line, write a query to return the name of all of the databases on your server:
The previous two commands were not executed immediately. You must type
GOon a new line to execute the previous commands:
Tip
To learn more about writing Transact-SQL statements and queries, see Tutorial: Writing Transact-SQL Statements.
Insert data
Next create a new table, Inventory, and insert two new rows.
From the sqlcmd command prompt, switch context to the new
TestDBdatabase:Create new table named
Inventory:Insert data into the new table:
Type
GOto execute the previous commands:
Select data
Now, run a query to return data from the Inventory table.
How To Install Sepm Symantec
From the sqlcmd command prompt, enter a query that returns rows from the
Inventorytable where the quantity is greater than 152:Execute the command:
Exit the sqlcmd command prompt
To end your sqlcmd session, type QUIT:
Performance best practices
After installing SQL Server on Linux, review the best practices for configuring Linux and SQL Server to improve performance for production scenarios. For more information, see Performance best practices and configuration guidelines for SQL Server on Linux.
Cross-platform data tools
In addition to sqlcmd, you can use the following cross-platform tools to manage SQL Server:
| Azure Data Studio | A cross-platform GUI database management utility. |
| Visual Studio Code | A cross-platform GUI code editor that run Transact-SQL statements with the mssql extension. |
| PowerShell Core | A cross-platform automation and configuration tool based on cmdlets. |
| mssql-cli | A cross-platform command-line interface for running Transact-SQL commands. |
Connecting from Windows
SQL Server tools on Windows connect to SQL Server instances on Linux in the same way they would connect to any remote SQL Server instance.
If you have a Windows machine that can connect to your Linux machine, try the same steps in this topic from a Windows command-prompt running sqlcmd. Just verify that you use the target Linux machine name or IP address rather than localhost, and make sure that TCP port 1433 is open. If you have any problems connecting from Windows, see connection troubleshooting recommendations.
For other tools that run on Windows but connect to SQL Server on Linux, see:
Other deployment scenarios
For other installation scenarios, see the following resources:
| Upgrade | Learn how to upgrade an existing installation of SQL Server on Linux |
| Uninstall | Uninstall SQL Server on Linux |
| Unattended install | Learn how to script the installation without prompts |
| Offline install | Learn how to manually download the packages for offline installation |
Tip
For answers to frequently asked questions, see the SQL Server on Linux FAQ.
Next steps
How To Install Sql Developer
-->This article explains how to install SQL Server with the Installation Wizard. It applies to SQL Server 2016 (13.x) and SQL Server 2017 (14.x).
This article provides a step-by-step procedure for installing a new instance of SQL Server by using the SQL Server Setup Installation Wizard. The Installation Wizard provides a single feature tree for installation of all SQL Server components so that you don't have to install them individually. To install the SQL Server components individually, see Install SQL Server.
For other ways to install SQL Server, see:
Get the installation media
How To Install Sepm With Sql Examples
The download location for SQL Server depends on the edition:
- SQL Server Enterprise, Standard, and Express Editions are licensed for production use. For the Enterprise and Standard Editions, contact your software vendor for the installation media. You can find purchasing information and a directory of Microsoft partners on the Microsoft purchasing website.
- Free editions are available at SQL Server downloads.
Prerequisites
Before you install SQL Server, review Planning a SQL Server installation.
Note
For local installations, you must run Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read and execute permissions on the remote share.
Install patch requirement
Microsoft has identified a problem with the Microsoft Visual C++ 2013 runtime binaries that are installed as a prerequisite by SQL Server 2016 and 2017. An update is available to fix this problem. If this update to the Visual C++ runtime binaries isn't installed, SQL Server may experience stability issues in certain scenarios. Before you install SQL Server, follow the instructions in the SQL Server release notes to see if your computer requires a patch for the Visual C++ runtime binaries.
Install Sepm
This is not applicable to SQL Server 2019.
To install SQL Server 2016 and 2017
Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, locate the root folder on the share, and then double-click Setup.exe.
The Installation Wizard runs the SQL Server Installation Center. To create a new installation of SQL Server, select Installation in the left navigation area, and then select New SQL Server standalone installation or add features to an existing installation.
On the Product Key page, select an option to indicate whether you're installing a free edition of SQL Server or a production version that has a PID key. For more information, see Editions and supported features of SQL Server 2017.
To continue, select Next.
On the License Terms page, review the license agreement. If you agree, select the I accept the license terms check box, and then select Next.
Note
SQL Server transmits information about your installation experience, as well as other usage and performance data to help Microsoft improve the product. To learn more about SQL Server data processing and privacy controls, see the privacy statement and Configure SQL Server to send feedback to Microsoft.
In the Global Rules page, Setup will automatically advance to the Product Updates page if there are no rule errors.
The Microsoft Update page will appear next if the Microsoft Update check box in Control Panel > All Control Panel Items > Windows Update > Change settings isn't selected. Selecting the Microsoft Update check box changes the computer settings to include the latest updates for all Microsoft products when you scan for Windows updates.
On the Product Updates page, the latest available SQL Server product updates are displayed. If no product updates are discovered, Setup doesn't display this page and automatically advances to the Install Setup Files page.
On the Install Setup Files page, Setup provides the progress of downloading, extracting, and installing the Setup files. If an update for Setup is found and you specify to include it, that update will also be installed. If no update is found, Setup will automatically advance.
On the Install Rules page, Setup checks for potential problems that might occur while running Setup. If failures occur, select an item in the Status column for more information. Otherwise, select Next.
If this is the first installation of SQL Server on the machine, Setup skips the Installation Type page and goes directly to the Feature Selection page. If SQL Server is already installed on the system, you can use the Installation Type page to select either to perform a new installation or to add features to an existing installation. To continue, select Next.
On the Feature Selection page, select the components for your installation. For example, to install a new instance of SQL Server Database Engine, select Database Engine Services.
A description for each component group appears in the Feature description pane after you select the feature name. You can select any combination of check boxes. For more information, see Editions and components of SQL Server 2016 or Editions and components of SQL Server 2017.
The prerequisites for the selected features are displayed in the Prerequisites for selected features pane. Setup installs the prerequisites that aren't already installed during the installation step described later in this procedure.
You can also specify a custom directory for shared components by using the field at the bottom of the Feature Selection page. To change the installation path for shared components, either update the path in the field at the bottom of the dialog box or select Browse to go to an installation directory. The default installation path is C:Program FilesMicrosoft SQL Servernnn.
Note
The path specified for the shared components must be an absolute path. The folder must not be compressed or encrypted. Mapped drives aren't supported.
SQL Server uses two directories for shared features:
- Shared feature directory
- Shared feature directory (x86)
Note
The path specified for each of the above options must be different.
The Feature Rules page automatically advances if all rules pass.
On the Instance Configuration page, specify whether to install a default instance or a named instance. For more information, see Instance configuration.
Instance ID: By default, the instance name is used as the instance ID. This ID is used to identify the installation directories and registry keys for your instance of SQL Server. The same behavior occurs for default instances and named instances. For a default instance, the instance name and instance ID are MSSQLSERVER. To use a nondefault instance ID, specify a different value in the Instance ID text box.
Note
Typical standalone instances of SQL Server, whether default or named instances, don't use a nondefault value for the instance ID.
All SQL Server service packs and upgrades apply to every component of an instance of SQL Server.
Installed instances: The grid shows the instances of SQL Server that are on the computer where Setup is running. If a default instance is already installed on the computer, you must install a named instance of SQL Server.
The workflow for the rest of the installation depends on the features that you've specified for your installation. Depending on your selections, you might not see all the pages.
Selecting to install the Polybase feature will add the PolyBase Configuration page to the SQL Server setup, displayed after the Instance Configuration page. PolyBase requires the Oracle JRE 7 Update 51 (at least), and if this hasn't already been installed, your installation will be blocked. On the Polybase Configuration page, you can choose to use the SQL Server as a standalone Polybase-enabled instance, or you can use this SQL Server as part of a PolyBase scale-out group. If you choose to use the scale-out group, you will need to specify a port range of up to 6 or more ports.
Use the Server Configuration - Service Accounts page to specify the logon accounts for SQL Server services. The actual services that you configure on this page depend on the features that you selected to install. For more information about configuration settings, see Installation Wizard help.
You can assign the same logon account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, start manually, or are disabled. We recommend you configure service accounts individually to provide the least privileges for each service. Make sure SQL Server services are granted the minimum permissions they must have to complete their tasks. For more information, see Configure Windows service accounts and permissions.
To specify the same logon account for all service accounts in this instance of SQL Server, provide the credentials in the fields at the bottom of the page.
Important
Do not use a blank password. Use a strong password.
Note
Starting with SQL Server 2016 (13.x), select the Grant Perform Volume Maintenance Task privilege to SQL Server Database Engine Service check box to allow the SQL Server Database Engine service account to use database instant file initialization.
Use the Server Configuration - Collation page to specify nondefault collations for the Database Engine and Analysis Services. For more information, see Collations and Unicode support.
Use the Database Engine Configuration - Server Configuration page to specify the following options:
Security Mode: Select Windows Authentication or Mixed Mode Authentication for your instance of SQL Server. If you select Mixed Mode Authentication, you must provide a strong password for the built-in SQL Server system administrator account.
After a device establishes a successful connection to SQL Server, the security mechanism is the same for both Windows authentication and mixed mode authentication. For more information, see Database Engine Configuration - Server Configuration page.
SQL Server Administrators: You must specify at least one system administrator for the instance of SQL Server. To add the account under which SQL Server Setup is running, select Add Current User. To add or remove accounts from the list of system administrators, select Add or Remove, and then edit the list of users, groups, or computers that have administrator privileges for the instance of SQL Server.
Use the Database Engine Configuration - Data Directories page to specify nondefault installation directories. To install to the default directories, select Next.
Important
If you specify nondefault installation directories, ensure that the installation folders are unique to this instance of SQL Server. None of the directories in this dialog box should be shared with directories from other instances of SQL Server.
For more information, see Database Engine Configuration - Data Directories page.
Use the Database Engine Configuration - TempDB page to configure the file size, number of files, nondefault installation directories, and file-growth settings for tempdb. For more information, see Database Engine Configuration - TempDB page.
Use the Database Engine Configuration - FILESTREAM page to enable FILESTREAM for your instance of SQL Server. For more information, see Database Engine Configuration - FILESTREAM page.
Use the Analysis Services Configuration - Account Provisioning page to specify the server mode and the users or accounts that have administrator permissions for Analysis Services. The server mode determines which memory and storage subsystems are used on the server. Different solution types run in different server modes. If you plan to run multidimensional cube databases on the server, select the default server mode option, Multidimensional and Data Mining.
You must specify at least one system administrator for Analysis Services:
To add the account under which SQL Server Setup is running, select Add Current User.
To add or remove accounts from the list of system administrators, select Add or Remove, and then edit the list of users, groups, or computers that have administrator privileges for Analysis Services.
For more information about server mode and administrator permissions, see Analysis Services Configuration - Account Provisioning page.
When you're finished editing the list, select OK. Verify the list of administrators in the configuration dialog box. After the list is complete, select Next.
Use the Analysis Services Configuration - Data Directories page to specify nondefault installation directories. To install to the default directories, select Next.
Important
When installing SQL Server, if you specify the same directory path for INSTANCEDIR and SQLUSERDBDIR, SQL Server Agent and Full Text Search won't start due to missing permissions.
If you specify nondefault installation directories, ensure that the installation folders are unique to this instance of SQL Server. None of the directories in this dialog box should be shared with directories from other instances of SQL Server.
For more information, see Analysis Services Configuration - Data Directories page.
Use the Distributed Replay Controller Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay controller service. Users that have administrative permissions have unlimited access to the Distributed Replay controller service.
To grant access permissions for the Distributed Replay controller service to the user who's running SQL Server Setup, select the Add Current User button.
To grant access permissions for the Distributed Replay controller service to other users, select the Add button.
To remove access permissions from the Distributed Replay controller service, select the Remove button.
To continue, select Next.
Use the Distributed Replay Client Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay client service. Users that have administrative permissions have unlimited access to the Distributed Replay client service.
Controller Name is optional. The default value is <blank>. Enter the name of the controller that the client computer will communicate with for the Distributed Replay client service:
If you've already set up a controller, enter the name of the controller while configuring each client.
If you haven't yet set up a controller, you can leave the controller name blank. However, you must manually enter the controller name in the client configuration file.
Specify the Working Directory for the Distributed Replay client service. The default working directory is <drive letter>:Program FilesMicrosoftSQL ServerDReplayClientWorkingDir.
Specify the Result Directory for the Distributed Replay client service. The default result directory is <drive letter>:Program FilesMicrosoftSQL ServerDReplayClientResultDir.
To continue, select Next.
The Ready to Install page shows a tree view of the installation options that you specified during Setup. On this page, Setup indicates whether the Product Update feature is enabled or disabled and the final update version.
To continue, select Install. SQL Server Setup first installs the required prerequisites for the selected features, then it installs the selected features.
During installation, the Installation Progress page provides status updates so that you can monitor the installation progress as Setup continues.
After installation, the Complete page provides a link to the summary log file for the installation and other important notes.
Important
Make sure you read the message from the Installation Wizard when you've finished with Setup. For more information, see View and read SQL Server Setup log files.
To complete the SQL Server installation process, select Close.
If you're instructed to restart the computer, do so now.
To install SQL Server 2019
Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, locate the root folder on the share, and then double-click Setup.exe.
The Installation Wizard runs the SQL Server Installation Center. To create a new installation of SQL Server, select Installation in the left navigation area, and then select New SQL Server standalone installation or add features to an existing installation.
On the Product Key page, select an option to indicate whether you're installing a free edition of SQL Server or a production version that has a PID key. For more information, see Editions and supported features of SQL Server 2017.
To continue, select Next.
On the License Terms page, review the license agreement. If you agree, select the I accept the license terms and privacy statement check box, and then select Next.
Note
SQL Server transmits information about your installation experience, as well as other usage and performance data to help Microsoft improve the product. To learn more about SQL Server data processing and privacy controls, see the privacy statement and Configure SQL Server to send feedback to Microsoft.
In the Global Rules page, Setup will automatically advance to the Product Updates page if there are no rule errors.
The Microsoft Update page will appear next if the Microsoft Update check box in Control Panel > All Control Panel Items > Windows Update > Change settings isn't selected. Selecting the Microsoft Update check box changes the computer settings to include the latest updates for all Microsoft products when you scan for Windows updates.
On the Product Updates page, the latest available SQL Server product updates are displayed. If no product updates are discovered, Setup doesn't display this page and automatically advances to the Install Setup Files page.
On the Install Setup Files page, Setup provides the progress of downloading, extracting, and installing the Setup files. If an update for Setup is found and you specify to include it, that update will also be installed. If no update is found, Setup will automatically advance.
On the Install Rules page, Setup checks for potential problems that might occur while running Setup. If failures occur, select an item in the Status column for more information. Otherwise, select Next.
If this is the first installation of SQL Server on the machine, Setup skips the Installation Type page and goes directly to the Feature Selection page. If SQL Server is already installed on the system, you can use the Installation Type page to select either to perform a new installation or to add features to an existing installation. To continue, select Next.
On the Feature Selection page, select the components for your installation. For example, to install a new instance of SQL Server Database Engine, select Database Engine Services.
A description for each component group appears in the Feature description pane after you select the feature name. You can select any combination of check boxes. For more information, see Editions and components of SQL Server 2016 or Editions and components of SQL Server 2017.
The prerequisites for the selected features are displayed in the Prerequisites for selected features pane. Setup installs the prerequisites that aren't already installed during the installation step described later in this procedure.
You can also specify a custom directory for shared components by using the field at the bottom of the Feature Selection page. To change the installation path for shared components, either update the path in the field at the bottom of the dialog box or select Browse to go to an installation directory. The default installation path is C:Program FilesMicrosoft SQL Servernnn.
Note
The path specified for the shared components must be an absolute path. The folder must not be compressed or encrypted. Mapped drives aren't supported.
SQL Server uses two directories for shared features:
- Shared feature directory
- Shared feature directory (x86)
Note
The path specified for each of the above options must be different.
The Feature Rules page automatically advances if all rules pass.
On the Instance Configuration page, specify whether to install a default instance or a named instance. For more information, see Instance configuration.
Instance ID: By default, the instance name is used as the instance ID. This ID is used to identify the installation directories and registry keys for your instance of SQL Server. The same behavior occurs for default instances and named instances. For a default instance, the instance name and instance ID are MSSQLSERVER. To use a nondefault instance ID, specify a different value in the Instance ID text box.
Note
Typical standalone instances of SQL Server, whether default or named instances, don't use a nondefault value for the instance ID.
All SQL Server service packs and upgrades apply to every component of an instance of SQL Server.
Installed instances: The grid shows the instances of SQL Server that are on the computer where Setup is running. If a default instance is already installed on the computer, you must install a named instance of SQL Server.
The workflow for the rest of the installation depends on the features that you've specified for your installation. Depending on your selections, you might not see all the pages.
Starting with SQL Server 2019, Polybase no longer requires that Oracle JRE 7 Update 51 (at least) be pre-installed on the computer prior to installing the feature. Selecting to install the Polybase feature will add the Java Install Location page to the SQL Server setup displayed after the Instance Configuration page. On the Java Install Location page, you can choose to install the Azul Zulu Open JRE included with the SQL Server 2019 installation, or provide a location of a different JRE or JDK that has already been installed on the computer.
Starting with SQL Server 2019, Java has been added with Language Extensions. Selecting to install the Java feature will add the Java Install Location page to the SQL Server setup dialog window, displayed after the Instance Configuration page. On the Java Install Location page, you can choose to install the Zulu Open JRE included with the SQL Server 2019 installation, or provide a location of a different JRE or JDK that has already been installed on the computer.
Use the Server Configuration - Service Accounts page to specify the logon accounts for SQL Server services. The actual services that you configure on this page depend on the features that you selected to install. For more information about configuration settings, see Installation Wizard help.
You can assign the same logon account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, start manually, or are disabled. We recommend you configure service accounts individually to provide the least privileges for each service. Make sure SQL Server services are granted the minimum permissions they must have to complete their tasks. For more information, see Configure Windows service accounts and permissions.
To specify the same logon account for all service accounts in this instance of SQL Server, provide the credentials in the fields at the bottom of the page.
Important
Do not use a blank password. Use a strong password.
Note
Starting with SQL Server 2016 (13.x), select the Grant Perform Volume Maintenance Task privilege to SQL Server Database Engine Service check box to allow the SQL Server Database Engine service account to use database instant file initialization.
Use the Server Configuration - Collation page to specify nondefault collations for the Database Engine and Analysis Services. For more information, see Collations and Unicode support.
Use the Database Engine Configuration - Server Configuration page to specify the following options:
Security Mode: Select Windows Authentication or Mixed Mode Authentication for your instance of SQL Server. If you select Mixed Mode Authentication, you must provide a strong password for the built-in SQL Server system administrator account.
After a device establishes a successful connection to SQL Server, the security mechanism is the same for both Windows authentication and mixed mode authentication. For more information, see Database Engine Configuration - Server Configuration page.
SQL Server Administrators: You must specify at least one system administrator for the instance of SQL Server. To add the account under which SQL Server Setup is running, select Add Current User. To add or remove accounts from the list of system administrators, select Add or Remove, and then edit the list of users, groups, or computers that have administrator privileges for the instance of SQL Server.
Use the Database Engine Configuration - Data Directories page to specify nondefault installation directories. To install to the default directories, select Next.
Important
If you specify nondefault installation directories, ensure that the installation folders are unique to this instance of SQL Server. None of the directories in this dialog box should be shared with directories from other instances of SQL Server.
For more information, see Database Engine Configuration - Data Directories page.
Use the Database Engine Configuration - TempDB page to configure the file size, number of files, nondefault installation directories, and file-growth settings for tempdb. For more information, see Database Engine Configuration - TempDB page.<<<<<<< HEAD
Use the Database Engine Configuration - MaxDOP page to specify your max degree of parallelism. This setting determines how many processors a single statement can use during execution. The recommended value is automatically calculated during installation. This page is only available in Setup starting with SQL Server 2019. For more information, see the Database Engine Configuration - MaxDOP page.
1d82c7efe18f86136247fb366df5030843199c19
Use the Analysis Services Configuration - Account Provisioning page to specify the server mode and the users or accounts that have administrator permissions for Analysis Services. The server mode determines which memory and storage subsystems are used on the server. Different solution types run in different server modes. If you plan to run multidimensional cube databases on the server, select the default server mode option, Multidimensional and Data Mining.
You must specify at least one system administrator for Analysis Services:
To add the account under which SQL Server Setup is running, select Add Current User.
To add or remove accounts from the list of system administrators, select Add or Remove, and then edit the list of users, groups, or computers that have administrator privileges for Analysis Services.
For more information about server mode and administrator permissions, see Analysis Services Configuration - Account Provisioning page.
When you're finished editing the list, select OK. Verify the list of administrators in the configuration dialog box. After the list is complete, select Next.
Use the Analysis Services Configuration - Data Directories page to specify nondefault installation directories. To install to the default directories, select Next.
Important
When installing SQL Server, if you specify the same directory path for INSTANCEDIR and SQLUSERDBDIR, SQL Server Agent and Full Text Search won't start due to missing permissions.
If you specify nondefault installation directories, ensure that the installation folders are unique to this instance of SQL Server. None of the directories in this dialog box should be shared with directories from other instances of SQL Server.
For more information, see Analysis Services Configuration - Data Directories page.
Use the Distributed Replay Controller Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay controller service. Users that have administrative permissions have unlimited access to the Distributed Replay controller service.
To grant access permissions for the Distributed Replay controller service to the user who's running SQL Server Setup, select the Add Current User button.
To grant access permissions for the Distributed Replay controller service to other users, select the Add button.
To remove access permissions from the Distributed Replay controller service, select the Remove button.
To continue, select Next.
Use the Distributed Replay Client Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay client service. Users that have administrative permissions have unlimited access to the Distributed Replay client service.
Controller Name is optional. The default value is <blank>. Enter the name of the controller that the client computer will communicate with for the Distributed Replay client service:
If you've already set up a controller, enter the name of the controller while configuring each client.
If you haven't yet set up a controller, you can leave the controller name blank. However, you must manually enter the controller name in the client configuration file.
Specify the Working Directory for the Distributed Replay client service. The default working directory is <drive letter>:Program FilesMicrosoftSQL ServerDReplayClientWorkingDir.
Specify the Result Directory for the Distributed Replay client service. The default result directory is <drive letter>:Program FilesMicrosoftSQL ServerDReplayClientResultDir.
To continue, select Next.
The Ready to Install page shows a tree view of the installation options that you specified during Setup. On this page, Setup indicates whether the Product Update feature is enabled or disabled and the final update version.
To continue, select Install. SQL Server Setup first installs the required prerequisites for the selected features, then it installs the selected features.
During installation, the Installation Progress page provides status updates so that you can monitor the installation progress as Setup continues.
After installation, the Complete page provides a link to the summary log file for the installation and other important notes.
Important
Make sure you read the message from the Installation Wizard when you've finished with Setup. For more information, see View and read SQL Server Setup log files.
To complete the SQL Server installation process, select Close.
If you're instructed to restart the computer, do so now.
Next steps
Configure your new SQL Server installation.
Sepm Symantec
To reduce the attackable surface area of a system, SQL Server selectively installs and enables key services and features. For more information, see Surface area configuration.