Install SQL Server from the Installation Wizard (Setup). 12 minutes to read. Contributors. In this article THIS TOPIC APPLIES TO: SQL Server (Windows only) Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse 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).
For content related to previous versions of SQL Server, see. This article provides a step-by-step procedure for installing a new instance of SQL Server using the SQL Server setup installation wizard. The SQL Server Installation Wizard provides a single feature tree for installation of all SQL Server components so that you do not have to install them individually. For more information about how to install the SQL Server components individually, see. These additional articles document other ways to install SQL Server:. Get the installation media The download location for SQL Server depends on the edition:.
SQL Server Enterprise, Standard, and Express Editions are licensed for production use. For 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. Free editions are available.
Prerequisites Before you install SQL Server, review articles in. 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 specific version of Microsoft VC 2013 Runtime binaries that are installed as a prerequisite by SQL Server. If this update to the VC runtime binaries is not installed, SQL Server may experience stability issues in certain scenarios. Before you install SQL Server follow the instructions at to see if your computer requires a patch for the VC runtime binaries. To install SQL Server. 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, click Installation in the left-hand navigation area, and then click New SQL Server stand-alone installation or add features to an existing installation.
On the Product Key page, select an option to indicate whether you are installing a free edition of SQL Server, or a production version of the product that has a PID key. For more information, see. To continue, click Next. On the License Terms page, review the license agreement and, if you agree, select the I accept the license terms check box, and then click 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 and. In the Global Rules window, the setup procedure will automatically advance to the Product Updates window 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 is not checked. Putting a check in the Microsoft Update page will change the computer settings to include the latest updates when you scan for Windows Update.
On the Product Updates page, the latest available SQL Server product updates are displayed. If no product updates are discovered, SQL Server Setup does not display this page and auto 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 SQL Server Setup is found, and is specified to be included, that update will also be installed. If no update is found, Setup will automatically advance. On Install Rules SQL Server Setup checks to identify potential problems that might occur while running Setup.
Sql Native Client 9
If failures occur, click in the Status column for more information. Otherwise click Next. If this is the first installation of SQL Server on the machine, the Installation Type page is skipped, and the installation goes directly to the Feature Selection page. However, if SQL Server is already installed on the system, on the Installation Type choose either to perform a new installation, or add features to an existing installation. On the Feature Selection page, select the components for your installation. Fnaf 1 cheat mode download pc. For example, to install a new instance of SQL Server database engine, check 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 and. The prerequisites for the selected features are displayed in the Prerequisites for selected features pane. SQL Server Setup will install the prerequisite that are not 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 click Browse to move to an installation directory. The default installation path is C: Program Files Microsoft SQL Server nnn.
The path specified for the shared components must be an absolute path. The folder must not be compressed or encrypted. Mapped drives are not supported. SQL Server uses two directories for shared features:. Shared feature directory.
![]()
Shared feature directory (x86) The path specified for each of the above options must be different. The Feature Rules window will automatically advance 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 ID — By default, the instance name is used as the Instance ID. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances.
For a default instance, the instance name and instance ID would be MSSQLSERVER. To use a non-default instance ID, specify a different value for Instance ID text box.
![]()
Note Typical stand-alone instances of SQL Server, whether default or named instances, do not use a non-default value for the Instance ID. All SQL Server service packs and upgrades will apply to every component of an instance of SQL Server. Installed instances — The grid shows instances of SQL Server that are on the computer where Setup is running.
Download Sql Server Native Client
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 have specified for your installation. You might not see all the pages, depending on your selections. Use the Server Configuration — Service Accounts page to specify login accounts for SQL Server services.
The actual services that are configured on this page depend on the features that you selected to install. You can assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled. Microsoft recommends that you configure service accounts individually to provide least privileges for each service, where SQL Server services are granted the minimum permissions they have to have to complete their tasks. For more information, see. To specify the same logon account for all service accounts in this instance of SQL Server, provide credentials in the fields at the bottom of the page. Note Starting with SQL Server 2016 (13.x), check the box Grant Perform Volume Maintenance Task privilege to SQL Server Database Engine Service to allow the SQL Server Database Engine service account to use.
Use the Server Configuration — Collation page to specify non-default collations for the Database Engine and Analysis Services. For more information, see. Use the Database Engine Configuration - Server Configuration page to specify the following:. 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.
For more information, see. 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, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for the instance of SQL Server. Use the Database Engine Configuration - Data Directories page to specify non-default installation directories. To install to default directories, click Next.
Important If you specify non-default 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. Use the Database Engine Configuration - FILESTREAM page to enable FILESTREAM for your instance of SQL Server. For more information, see. Use the Database Engine Configuration - TempDB page to configure file size, number of files, non-default installation directories, and file-growth settings for TempDB. For more information see.
Use the Analysis Services Configuration — Account Provisioning page to specify the server mode and the users or accounts that will have administrator permissions for Analysis Services. 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, choose the default option, Multidimensional and Data Mining server mode. Regarding administrator permissions, you must specify at least one system administrator for Analysis Services.
To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for Analysis Services. For more information about server mode and administrator permissions, see. When you are finished editing the list, click OK.
Verify the list of administrators in the configuration dialog box. When the list is complete, click Next. Use the Analysis Services Configuration — Data Directories page to specify non-default installation directories.
To install to default directories, click Next. Important When installing SQL Server, if you specify the same directory path for INSTANCEDIR and SQLUSERDBDIR, SQL Server Agent and Full Text Search do not start due to missing permissions. If you specify non-default 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.
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 will have unlimited access to the Distributed Replay controller service.
Click the Add Current User button to add the users to whom you want to grant access permissions for the Distributed Replay controller service. Click the Add button to add access permissions for the Distributed Replay controller service.
Click the Remove button to remove access permissions from the Distributed Replay controller service. To continue, click 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 will have unlimited access to the Distributed Replay client service. Controller Name is an optional parameter, and the default value is. Enter the name of the controller that the client computer will communicate with for the Distributed Replay client service. Note the following:.
If you have already set up a controller, enter the name of the controller while configuring each client. If you have not 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: Program Files Microsoft SQL Server DReplayClient WorkingDir.
Specify the Result Directory for the Distributed Replay client service. The default result directory is: Program Files Microsoft SQL Server DReplayClient ResultDir. To continue, click Next. The Ready to Install page shows a tree view of installation options that were specified during Setup. On this page, Setup indicates whether the Product Update feature is enabled or disabled and the final update version. To continue, click Install. SQL Server Setup will first install the required prerequisites for the selected features followed by the feature installation.
During installation, the Installation Progress page provides status so that you can monitor 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. To complete the SQL Server installation process, click Close. If you are instructed to restart the computer, do so now.
It is important to read the message from the Installation Wizard when you have finished with Setup. For more information, see. Next steps Configure your new SQL Server installation. To reduce the attackable surface area of a system, SQL Server selectively installs and enables key services and features. For more information, see.
Installing SQL Server Native Client. 2 minutes to read. Contributors. In this article THIS TOPIC APPLIES TO: SQL Server Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse For content related to previous versions of SQL Server, see. Microsoft SQL Server Native Client 11.0 is installed when you install SQL Server 2016 (13.x). There is no SQL Server 2016 Native Client.
Where Is Sql Native Client Installed
For more information, see. You can also get sqlncli.msi from the SQL Server 2012 Feature Pack web page. To download the most recent version of the the SQL Server Native Client, go to.
If a previous version of SQL Server Native Client earlier than SQL Server 2012 is also installed on the computer, SQL Server Native Client 11.0 will be installed side-by-side with the earlier version. The SQL Server Native Client files (sqlncli11.dll, sqlnclir11.rll, and s11chsqlncli.chm) are installed to the following location:%SYSTEMROOT% system32.
Quantum Jumping – Peek. Module 7 quantum jumping meditations.
Pdf redirect pro. HI there, I installed SharePoint (MOSS) 2007 on a Win 2003 SP2 server using SQL Server 2005 ENT and later installed SQL 2005 SP2. At the time I didn't install the client tools on the server (which apparently I should have). I now attempted to install client tools on the server but I got an error message 'SQL Server Native client failed because a higher version already exists on this machine. To proceed, uninstall the higher version and then run SQL Server Native client setup' I failed to find on the net a client.msi that included SP2 and a bit of Goggle research pointed to the fact that I cannot easily uninstall SQL 2005 SP2. Log story short I am at a dead end: I cannot install client due to an higher version and cannot uninstall the higher version.
Any suggestions on how to get the client tools installed on the server. Thank you, Luis.
Hardware and Software Requirements for Installing SQL Server. 10 minutes to read. Contributors.
In this article THIS TOPIC APPLIES TO: SQL Server (Windows only) Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse The article lists the minimum hardware and software requirements to install and run SQL Server on the Windows operating system. SQL Server 2017 (14.x) introduces support for SQL Server on Linux. For information, see. This article applies to SQL Server 2016 (13.x) and later. For content related to previous versions of SQL Server, see. Try it out:.
Download SQL Server from the. Spin up a Virtual Machine with already installed. The following considerations apply to all editions:. We recommend that you run SQL Server on computers with the NTFS or ReFS file formats.
Installing SQL Server on a computer with FAT32 file system is supported but not recommended as it is less secure than the NTFS or ReFS file systems. SQL Server Setup will block installations on read-only, mapped, or compressed drives. Installation fails if you launch setup through Remote Desktop Connection with the media on a local resource in the RDC client. To install remotely the media must be on a network share or local to the physical or virtual machine. SQL Server installation media may be either on a network share, a mapped drive, a local drive, or presented as an ISO to a virtual machine. SQL Server Management Studio installation requires installing.NET 4.6.1 as a prerequisite.NET 4.6.1 will be automatically installed by setup when SQL Server Management Studio is selected.
SQL Server Setup installs the following software components required by the product:. SQL Server Native Client. SQL Server Setup support files.
For minimum version requirements to install SQL Server on Windows Server 2012 or Windows 8, see. Hardware and Software Requirements The following requirements apply to all installations: Component Requirement.NET Framework SQL Server 2016 (13.x) RC1 and later require.NET Framework 4.6 for the Database Engine, Master Data Services, or Replication. SQL Server 2016 (13.x) setup automatically installs.NET Framework. You can also manually install.NET Framework from. For more information, recommendations, and guidance about.NET Framework 4.6 see. Windows 8.1, and Windows Server 2012 R2 require before installing.NET Framework 4.6.
Network Software Supported operating systems for SQL Server have built-in network software. Named and default instances of a stand-alone installation support the following network protocols: Shared memory, Named Pipes, TCP/IP and VIA. Note: VIA protocol is not supported on failover clusters. Clients or applications running on the same node of the failover cluster as the SQL Server instance, can use Shared Memory protocol to connect to SQL Server using its local pipe address. However this type of connection is not cluster-aware and will fail after an instance failover. It is therefore not recommended and should only be used in very specific scenarios. Important: The VIA protocol is deprecated.
This feature is in maintenance mode and may be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. For more information about Network Protocols and Network Libraries, see.
Hard Disk SQL Server requires a minimum of 6 GB of available hard-disk space. Disk space requirements will vary with the SQL Server components you install. For more information, see later in this article.
For information on supported storage types for data files, see. Drive A DVD drive, as appropriate, is required for installation from disc.
![]()
Monitor SQL Server requires Super-VGA (800x600) or higher resolution monitor. Internet Internet functionality requires Internet access (fees may apply). Important There are additional hardware and software requirements for the PolyBase feature. For more information, see. Processor, Memory, and Operating System Requirements The following memory and processor requirements apply to all editions of SQL Server: Component Requirement Memory. Minimum: Express Editions: 512 MB All other editions: 1 GB Recommended: Express Editions: 1 GB All other editions: At least 4 GB and should be increased as database size increases to ensure optimal performance.
Processor Speed Minimum: x64 Processor: 1.4 GHz Recommended: 2.0 GHz or faster Processor Type x64 Processor: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support. Note Installation of SQL Server is supported on x64 processors only. It is no longer supported on x86 processors. The minimum memory required for installing the Data Quality Server component in Data Quality Services (DQS) is 2 GB of RAM, which is different from the SQL Server minimum memory requirement. For information about installing DQS, see.
WOW64 Support: WOW64 (Windows 32-bit on Windows 64-bit) is a feature of 64-bit editions of Windows that enables 32-bit applications to run natively in 32-bit mode. Applications function in 32-bit mode, even though the underlying operating system is a 64-bit operating system. WOW64 is not supported for SQL Server installations. However, Management Tools are supported in WOW64. Operating System Support: The SQL Server editions are classified into the following:. Note Exceptions to the operating system support noted in this section are the following Business Intelligence features for SQL Server 2016 (13.x) and earlier, which can be installed on Windows Server 2008 R2 SP1 or later:.
Reporting Services - SharePoint. Reporting Services Add-in for SharePoint products Features Supported on 32-bit Client Operating Systems Windows client operating systems, for example Windows 10 and Windows 8.1 are available as 32-bit or 64-bit architectures. All SQL Server features are supported on 64-bit client operating systems. On supported 32-bit client operating systems Microsoft supports the following features:. Data Quality Client. Client Tools Connectivity.
Integration Services. Client Tools Backwards Compatibility. Client Tools SDK. Documentation Components. Distributed Replay Components. Distributed Replay Controller. Distributed Replay Client.
SQL Client Connectivity SDK Windows Server 2008 R2 and later server operating systems are not available as 32-bit architectures. All supported server operating systems are only available as 64-bit. All features are supported on 64-bit server operating systems. Warning SQL Server failover cluster installation supports Local Disk only for installing the tempdb files. Ensure that the path specified for the tempdb data and log files is valid on all the cluster nodes. During failover, if the tempdb directories are not available on the failover target node, the SQL Server resource will fail to come online. Installing SQL Server on a Domain Controller For security reasons, we recommend that you do not install SQL Server on a domain controller.
SQL Server Setup will not block installation on a computer that is a domain controller, but the following limitations apply:. You cannot run SQL Server services on a domain controller under a local service account. After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller. After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
SQL Server failover cluster instances are not supported where cluster nodes are domain controllers. SQL Server is not supported on a read-only domain controller. SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail. A SQL Server failover cluster instance is not not supported in an environment where only a read-only domain controller is accessible.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |