Configure SQL Server on a Server Core Installation
Applies To: SQL Server 2016
This topic covers details about configuring SQL Server on a Server Core installation of Windows Server 2008 R2 SP1. Refer the following sections:
The section provides references to the topics that help configure and manage a Server Core installation.
Not all features of SQL Server 2016 are supported in Server Core mode. Some of these features can be installed on a client computer or a different server that is not running Server Core, and connected to the Database Engine services installed on Server Core.
For more information about configuring and managing a Server Core installation remotely, see the following topics:
Windows Server 2008 R2: Best Practices for Server Core Deployments (http://go.microsoft.com/fwlink/?LinkID=245957)
Configuring a Server Core installation: Overview (http://go.microsoft.com/fwlink/?LinkId=245958)
Configuring a Server Core installation of Windows Server 2008 R2 with Sconfig.cmd (http://go.microsoft.com/fwlink/?LinkId=245959)
Installing a server role on a server running a Server Core installation of Windows Server 2008 R2: Overview (http://go.microsoft.com/fwlink/?LinkId=245960)
Installing Windows Features on a server running a Server Core installation of Windows Server 2008 R2: Overview (http://go.microsoft.com/fwlink/?LinkId=245961)
Managing a Server Core installation: Overview (http://go.microsoft.com/fwlink/?LinkId=245962)
Administering a Server Core installation (http://go.microsoft.com/fwlink/?LinkId=245963)
This section provides information about installing updates for SQL Server 2016 on a Windows Server Core machine. We recommend that customers evaluate and install latest SQL Server updates in a timely manner to make sure that systems are up-to-date with the most recent security updates. For more information about installing SQL Server 2016 on a Windows Server Core machine, see Install SQL Server 2016 on Server Core.
The following are the two scenarios for installing product updates:
SQL Server Setup supports only command prompt installations on Server Core operating system. For more information, see Install SQL Server 2016 from the Command Prompt.
SQL Server setup integrates the latest product updates with the main product installation so that the main product and its applicable updates are installed at the same time.
After Setup finds the latest versions of the applicable updates, it downloads and integrates them with the current SQL Server setup process. Product Update can pull in a cumulative update, service pack, or service pack plus cumulative update.
Specify the UpdateEnabled, and UpdateSource parameters to include the latest product updates with the main product installation. Refer the following example to enable product updates during the SQL Server Setup:
Setup.exe /qs /ACTION=Install /FEATURES=SQLEngine,Replication /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="<StrongPassword>" /SQLSYSADMINACCOUNTS="<DomainName\UserName>" /AGTSVCACCOUNT="NT AUTHORITY\Network Service" /UpdateEnabled=True /UpdateSource=”<SourcePath>” /IACCEPTSQLSERVERLICENSETERMS
On an installed instance of SQL Server 2016, we recommend that you apply the latest security updates and critical updates including General Distribution Releases (GDRs), and Service Packs (SPs). Individual Cumulative updates and security updates should be adopted on a case-by-case, "as-needed" basis. Evaluate the update; if it's needed, then apply it.
Apply an update at a command prompt, replacing <package_name> with the name of your update package:
Update a single instance of SQL Server and all shared components. You can specify the instance either by using the InstanceName parameter or the InstanceID parameter.
<package_name>.exe /qs /IAcceptSQLServerLicenseTerms /Action=Patch /InstanceName=MyInstance
Update SQL Server shared components only:
<package_name>.exe /qs /IAcceptSQLServerLicenseTerms /Action=Patch
Update all instances of SQL Server on the computer and all shared components:
<package_name>.exe /qs /IAcceptSQLServerLicenseTerms /Action=Patch /AllInstances
The sqlservr Application application starts, stops, pauses, and continues an instance of SQL Server from a command prompt.
You can also use Net services to start and stop the SQL Server services.
Being enabled for AlwaysOn Availability Groups is a prerequisite for a server instance to use availability groups as a high availability and disaster recovery solution. For more information about managing the AlwaysOn Availability Groups, see Enable and Disable AlwaysOn Availability Groups (SQL Server).
These steps are meant to be performed on a PC running the client edition of Windows 7 or later, or another server that has the Server Graphical Shell installed (i.e. a full installation of Windows Server 2008 R2 or a Windows Server 2012 installation with the Server Graphical Shell feature enabled).
Open Computer Management. To open Computer Management do one of the following:
On Windows 7, Windows Server 2008, or Windows Server 2008 R2:
Click Start, click All Programs, click Administrative Tools, and then click Computer Management.
Click Start, click Run, type COMPMGMT.MSC, and then click OK.
On Windows Server 2012 with Server Graphical Shell enabled:
Move your mouse to the bottom-left corner of the screen and right-click when you see the Start overlay.
Select Computer Management from the context menu.
In the console tree, right-click Computer Management, and then click Connect to another computer.
In the Select Computer dialog box, type the name of the Server Core machine that you want to manage, or click Browse to find it, and then click OK.
In the console tree, under Computer Management of the Server Core machine, click Services and Applications.
Double click SQL Server Configuration Manager.
In SQL Server Configuration Manager, click SQL Server Services, right-click SQL Server (<instance name>), where <instance name> is the name of a local server instance for which you want to enable AlwaysOn Availability Groups, and click Properties.
Select the AlwaysOn High Availability tab.
Verify that Windows failover cluster name field contains the name of the local failover cluster node. If this field is blank, this server instance currently does not support AlwaysOn Availability Groups. Either the local computer is not a cluster node, the WSFC cluster has been shut down, or this edition of SQL Server 2016 that does not support AlwaysOn Availability Groups.
Select the Enable AlwaysOn Availability Groups check box, and click OK.
SQL Server Configuration Manager saves your change. Then, you must manually restart the SQL Server service. This enables you to choose a restart time that is best for your business requirements. When the SQL Server service restarts, AlwaysOn will be enabled, and the IsHadrEnabled server property will be set to 1.
The PowerShell Cmdlet, Enable-SqlAlwaysOn, is used to enable AlwaysOn Availability Group on an instance of SQL Server. If AlwaysOn Availability Groups is enable while the SQL Server service is running, the Database Engine service must be restarted for the change to complete. Unless you specify the -Force parameter, the cmdlet prompts you to ask whether you wish to restart the service; if cancelled, no operation occurs.
You must have Administrator permissions to execute this cmdlet.
You can use one of the following syntaxes to enable AlwaysOn Availability Groups for an instance of SQL Server:
Enable-SqlAlwaysOn [-Path <string>] [-Credential <PSCredential>] [-Force] [-NoServiceRestart] [-Confirm] [-WhatIf] [<Commom Parameters>]
Enable-SqlAlwaysOn -InputObject <Server> [-Credential <PSCredential>] [-Force] [-NoServiceRestart] [-Confirm] [-WhatIf] [<Commom Parameters>]
Enable-SqlAlwaysOn [-ServerInstance <string>] [-Credential <PSCredential>] [-Force] [-NoServiceRestart] [-Confirm] [-WhatIf] [<Commom Parameters>]
The following PowerShell command enables AlwaysOn Availability Groups on an instance of SQL Server (Machine\Instance):
Enable-SqlAlwaysOn -Path SQLSERVER:\SQL\Machine\Instance
Perform the actions described below to configure remote access of a SQL Server 2016 instance that is running on Windows Server 2008 R2 Server Core SP1.
To enable remote connections, use SQLCMD.exe locally and execute the following statements against the Server Core instance:
EXEC sys.sp_configure N'remote access', N'1'
RECONFIGURE WITH OVERRIDE
By default, the Browser service is disabled. If it is disabled on an instance of SQL Server running on Server Core, run the following command from the command prompt to enable it:
sc config SQLBROWSER start= auto
After it is enabled, run the following command from the command prompt to start the service:
net start SQLBROWSER
To create exceptions for SQL Server access in Windows Firewall, follow the steps specified in Configure the Windows Firewall to Allow SQL Server Access.
The TCP/IP protocol can be enabled through Windows PowerShell for an instance of SQL Server on Server Core. Follow these steps:
On the computer that is running Windows Server 2008 R2 Server Core SP1, launch Task Manager.
On the Applications tab, click New Task.
In the Create New Task dialog box, type sqlps.exe in the Open field and then click OK. This opens the Microsoft SQL Server Powershell window.
In the Microsoft SQL Server Powershell window, run the following script to enable the TCP/IP protocol:
$smo = 'Microsoft.SqlServer.Management.Smo.' $wmi = new-object ($smo + 'Wmi.ManagedComputer') # Enable the TCP protocol on the default instance. If the instance is named, replace MSSQLSERVER with the instance name in the following line. $uri = "ManagedComputer[@Name='" + (get-item env:\computername).Value + "']/ServerInstance[@Name='MSSQLSERVER']/ServerProtocol[@Name='Tcp']" $Tcp = $wmi.GetSmoObject($uri) $Tcp.IsEnabled = $true $Tcp.Alter() $Tcp
On a remote machine, start SQL Server Profiler and select New Trace from the File menu, the application displays a Connect to Server dialog box where you can specify the SQL Server instance, residing on the Server Core machine, to which you want to connect. For more information, see Start SQL Server Profiler.
For more information on the permissions required to run SQL Server Profiler, see Permissions Required to Run SQL Server Profiler.
For additional details about SQL Server Profiler, see SQL Server Profiler.
You can use SQL Server Management Studio or Transact-SQL remotely to define an audit. After the audit is created and enabled, the target will receive entries. For more information about creating and managing SQL Server audits, see SQL Server Audit (Database Engine).
You can use the following command prompt utilities that enable you to script SQL Server operations on a Server Core machine. The following table contains a list of command prompt utilities that ship with SQL Server for Server Core:
|bcp Utility||Used to copy data between an instance of MicrosoftSQL Server and a data file in a user-specified format.||<drive>:\Program Files\Microsoft SQL Server\130\Tools\Binn|
|dtexec Utility||Used to configure and execute an Integration Services package.||<drive>:\Program Files\Microsoft SQL Server\130\DTS\Binn|
|dtutil Utility||Used to manage SSIS packages.||<drive>:\Program Files\Microsoft SQL Server\130\DTS\Binn|
|osql Utility||Allows you to enter Transact-SQL statements, system procedures, and script files at the command prompt.||<drive>:\Program Files\Microsoft SQL Server\130\Tools\Binn|
|sqlagent90 Application||Used to start SQL Server Agent from a command prompt.||<drive>:\Program Files\MicrosoftSQL Server\<instance_name>\MSSQL\Binn|
|sqlcmd Utility||Allows you to enter Transact-SQL statements, system procedures, and script files at the command prompt.||<drive>:\Program Files\Microsoft SQL Server\130\Tools\Binn|
|SQLdiag Utility||Used to collect diagnostic information for Microsoft Customer Service and Support.||<drive>:\Program Files\Microsoft SQL Server\130\Tools\Binn|
|sqlmaint Utility||Used to execute database maintenance plans created in previous versions of SQL Server.||<drive>:\Program Files\MicrosoftSQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn|
|sqlps Utility||Used to run PowerShell commands and scripts. Loads and registers the SQL Server PowerShell provider and cmdlets.||<drive>:\Program Files\Microsoft SQL Server\130\Tools\Binn|
|sqlservr Application||Used to start and stop an instance of Database Engine from the command prompt for troubleshooting.||<drive>:\Program Files\MicrosoftSQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn|
You can use SQLdiag Utility to collect logs and data files from SQL Server and other types of servers, and use it to monitor your servers over time or troubleshoot specific problems with your servers. SQLdiag is intended to expedite and simplify diagnostic information gathering for Microsoft Customer Support Services.
You can launch the utility on the administrator command prompt on the Server Core, using the syntax specified in the topic: SQLdiag Utility.