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.
Sql Native Client 9
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.
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.
Generally, a download manager enables downloading of large files or multiples files in one session. Many web browsers, such as Internet Explorer 9, include a download manager. Stand-alone download managers also are available, including the Microsoft Download Manager. If you do not have a download manager installed, and still want to download the file(s) you've chosen, please note:. You may not be able to download multiple files at the same time. In this case, you will have to download the files individually. (You would have the opportunity to download individual files on the 'Thank you for downloading' page after completing your download.).
Files larger than 1 GB may take much longer to download and might not download correctly. You might not be able to pause the active downloads or resume downloads that have failed. The Microsoft Download Manager solves these potential problems. It gives you the ability to download multiple files at one time and download large files quickly and reliably. It also allows you to suspend active downloads and resume downloads that have failed. Microsoft Download Manager is free and available for download now. Microsoft ODBC Driver 11 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2005, 2008, 2008 R2, SQL Server 2012, SQL Server 2014 and Windows Azure SQL Database.
Microsoft ODBC Driver 11 for SQL Server should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2012 features. This redistributable installer for Microsoft ODBC Driver 11 for SQL Server installs the client components needed during run time to take advantage of new SQL Server 2012 features, and optionally installs the header files needed to develop an application that uses the ODBC API.
![]()
Generally, a download manager enables downloading of large files or multiples files in one session. Many web browsers, such as Internet Explorer 9, include a download manager. Stand-alone download managers also are available, including the Microsoft Download Manager. If you do not have a download manager installed, and still want to download the file(s) you've chosen, please note:. You may not be able to download multiple files at the same time. In this case, you will have to download the files individually. (You would have the opportunity to download individual files on the 'Thank you for downloading' page after completing your download.).
Files larger than 1 GB may take much longer to download and might not download correctly. You might not be able to pause the active downloads or resume downloads that have failed. The Microsoft Download Manager solves these potential problems.
It gives you the ability to download multiple files at one time and download large files quickly and reliably. It also allows you to suspend active downloads and resume downloads that have failed.
Microsoft Download Manager is free and available for download now. Download the appropriate file by clicking one of the links below, then run the downloaded file to install thSat package. Each package indicates the audience(s) for which it was intended, as follows: Customer: An individual may want to install this for additional licensed functionality such as interoperability.
Partner: An ISV may want to ship this as a redistributable component as part of their application. Developer: A programmer may want to install this to support application development.
Note: To archive a copy of the license terms, prior to accepting them, copy and paste the terms to a word processing program, then print or save the file to your favorite directory. Microsoft ADOMD.NET ADOMD.NET is a Microsoft.NET Framework object model that enables software developers to create client-side applications that browse metadata and query data stored in Microsoft SQL Server 2008 Analysis Services. ADOMD.NET is a Microsoft ADO.NET provider with enhancements for online analytical processing (OLAP) and data mining.
Note:The English ADOMD.NET setup package installs support for all SQL Server 2008 languages. Audience(s): Customer, Partner, Developer X86 Package(SQLSERVER2008ASADOMD10.msi) X64 Package (SQLSERVER2008ASADOMD10.msi) IA64 Package(SQLSERVER2008ASADOMD10.msi) Microsoft Analysis Management Objects Analysis Management Objects (AMO) is a.NET Framework object model that enables software developers to create client-side applications to manage and administer Analysis Services objects. Audience(s): Customer, Partner, Developer X86 Package(SQLSERVER2008ASAMO10.msi) X64 Package (SQLSERVER2008ASAMO10.msi) IA64 Package(SQLSERVER2008ASAMO10.msi) Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider The Analysis Services 10.0 OLE DB Provider is a COM component that software developers can use to create client-side applications that browse metadata and query data stored in Microsoft SQL Server 2008 Analysis Services. This provider implements both the OLE DB specification and the specification’s extensions for online analytical processing (OLAP) and data mining. Note: Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider requires Microsoft Core XML Services (MSXML) 6.0, also available on this page. Audience(s): Customer, Partner, Developer X86 Package(SQLServer2008ASOLEDB10.msi) X64 Package (SQLServer2008ASOLEDB10.msi) IA64 Package(SQLServer2008ASOLEDB10.msi) Microsoft SQL Server 2005 Backward Compatibility Components The SQL Server Backward Compatibility package includes the latest versions of the Data Transformation Services 2000 runtime (DTS), SQL Distributed Management Objects (SQL-DMO), Decision Support Objects (DSO), and SQL Virtual Device Interface (SQLVDI). These versions have been updated for compatibility with both SQL Server 2005 and SQL Server 2008 and include all fixes shipped through SQL Server 2000 Service Pack 4 (SP4) and SQL Server 2005 SP2.
Audience(s): Customer, Partner, Developer X86 Package (SQLServer2005BC.msi) X64 Package (SQLServer2005BC.msi) IA64 Package (SQLServer2005BC.msi) Microsoft SQL Server 2008 Command Line Utilities The SQLCMD utility allows users to connect to, send Transact-SQL batches from, and output rowset information from SQL Server 7.0, SQL Server 2000, SQL Server 2005, and SQL Server 2008 instances. The bcp utility bulk copies data between an instance of Microsoft SQL Server 2008 and a data file in a user-specified format. The bcp utility can be used to import large numbers of new rows into SQL Server tables or to export data out of tables into data files. Note: This component requires both and Microsoft SQL Server Native Client (which is another component available from this page). Audience(s): Customer, Partner, Developer X86 Package(SqlCmdLnUtils.msi) X64 Package (SqlCmdLnUtils.msi) IA64 Package(SqlCmdLnUtils.msi) SQL Server Compact 3.5 SP1 SQL Server Compact is a free, easy-to-use embedded database engine that lets developers build robust Microsoft Windows desktop and mobile applications that run on all Windows operating systems including Windows XP, Vista, Pocket PC, and Smartphone.
Run the Microsoft Windows installer file (MSI) to install the product. The single setup program will install the provider and tools on x86 and x64 computers. The package includes product updates in the form of an integrated Service Pack 1. Read the installation guide and Readme for more information.
Audience(s): Customer, Partner, Developer Microsoft Connector 1.0 for SAP BI The Microsoft Connector for SAP BI is a set of managed components for transferring data to or from an SAP NetWeaver BI version 7.0 system. The component is designed to be used with the Enterprise and Developer editions of SQL Server 2008 Integration Services.
To install the component, run the platform-specific installer for x86, x64, or Itanium computers respectively. For more information see the Readme and the installation topic in the Help file. Audience(s): Customer, Developer X86 Package(SapBI.msi) X64 Package (SapBI.msi) IA64 Package(SapBI.msi) Microsoft SQL Server 2008 Data Mining Add-ins for Microsoft Office 2007 Microsoft SQL Server 2008 Data Mining Add-ins for Microsoft Office 2007 enables you to take advantage of SQL Server 2008 predictive analytics in Office Excel 2007 and Office Visio 2007.
The download includes the following components:. Table Analysis Tools for Excel: This add-in provides easy-to-use tools that leverage SQL Server 2008 data mining features to perform powerful analytics on your spreadsheet data. Two new tools have been added for this release: Prediction Calculator and Shopping Basket Analysis. Data Mining Client for Excel: This add-in enables you to go through the full data mining model development lifecycle within Excel 2007 using your spreadsheet data or external data accessible through your SQL Server 2008 Analysis Services instance. This release adds support for new SQL Server 2008 data mining features including holdout and cross-validation, a new Document Model wizard, and improvements to existing wizards.
Data Mining Templates for Visio: This add-in enables you to render and share your mining models as annotatable Visio 2007 drawings. Audience(s): Customer, Partner, Developer Package(SQLServer2008DMAddin.msi) Microsoft SQL Server 2008 Datamining Viewer Controls The Data Mining Web Controls Library is a set of Microsoft Windows Forms controls that enable software developers to display data mining models created using Microsoft SQL Server 2008 Analysis Services in their client-side applications. The controls in this library display the patterns that are contained in Analysis Services mining models. Note:Microsoft SQL Server 2008 Datamining Viewer Controls requires Microsoft ADOMD.NET, also available on this page. Audience(s): Customer, Partner, Developer X86 Package(SQLServer2008DMViewer.msi) Microsoft SQL Server Driver for PHP 1.0 The SQL Server Driver for PHP 1.0 is a PHP 5 extension that allows for accessing data in all Editions of SQL Server 2005 and SQL Server 2008 (including Express Editions) from within PHP scripts. The driver provides a procedural interface for accessing data and makes use of PHP features, including PHP streams to read and write large objects.
With this release, the source code for the driver is available here:. The SQL Server Driver for PHP 1.0 relies on the Microsoft SQL Server 2005 Native Client to communicate with SQL Server. For more information about SQL Server 2005 Native Client, visit the on MSDN. Audience(s): Developer, DBA Microsoft Core XML Services (MSXML) 6.0 Microsoft Core XML Services (MSXML) 6.0 is the latest version of the native XML processing stack.
MSXML 6.0 provides standards-conformant implementations of XML 1.0, XML Schema (XSD) 1.0, XPath 1.0, and XSLT 1.0. In addition, it offers 64-bit support, increased security for working with untrusted XML data, and improved reliability over previous versions of MSXML. Audience(s): Partner, Developer Microsoft SQL Server 2005 JDBC Driver 1.2 In its continued commitment to interoperability, Microsoft has released a Java Database Connectivity (JDBC) driver for SQL Server. The SQL Server 2005 JDBC Driver v1.2 download is available to all SQL Server users at no additional charge, and provides access to SQL Server 2000, SQL Server 2005, and SQL Server 2008 from any Java application, application server, or Java-enabled applet. This is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in J2EE (Java2 Enterprise Edition). Audience(s): Partner, Developer Microsoft SQL Server 2008 Management Objects The SQL Server Management Objects (SMO) is a.NET Framework object model that enables software developers to create client-side applications to manage and administer SQL Server objects and services. This object model will work with SQL Server 2000, SQL Server 2005 and SQL Server 2008.
Note: Microsoft SQL Server 2008 Management Objects Collection requires Microsoft Core XML Services (MSXML) 6.0, Microsoft SQL Server Native Client, and Microsoft SQL Server System CLR Types. These are available on this page. Audience(s): Customer, Partner, Developer X86 Package (SharedManagementObjects.msi) X64 Package (SharedManagementObjects.msi) IA64 Package (SharedManagementObjects.msi) SQL Server Remote Blob Store The SQL Server Remote Blob Store is a method for storing blobs of unstructured data in an external Content Addressable data store. The component consists of a client-side DLL that is linked into a user application, as well as a set of stored procedures to be installed on SQL Server. Run the self-extracting download package to create an installation folder. The setup program contained there will install RBS on X86, X64, and Itanium-based computers. Audience(s): Developer, DBA X86 Package (RBS.msi) X64 Package (RBS.msi) IA64 Package (RBS.msi) Microsoft SQL Server 2008 Native Client Microsoft SQL Server 2008 Native Client (SQL Server Native Client) is a single dynamic-link library (DLL) containing both the SQL OLE DB provider and SQL ODBC driver.
It contains run-time support for applications using native-code APIs (ODBC, OLE DB and ADO) to connect to Microsoft SQL Server 2000, 2005, or 2008. SQL Server Native Client should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2008 features. This redistributable installer for SQL Server Native Client installs the client components needed during run time to take advantage of new SQL Server 2008 features, and optionally installs the header files needed to develop an application that uses the SQL Server Native Client API. Audience(s): Customer, Partner, Developer X86 Package (sqlncli.msi) X64 Package (sqlncli.msi) IA64 Package (sqlncli.msi) Microsoft SQL Server 2008 Policies Microsoft SQL Server 2008 Policies are examples of how you can take advantage of Policy Based Management. These policies will help you follow some of the SQL Server best practices and avoid common pitfalls. For more information, please see in SQL Server 2008 Books Online.
Note: This component also requires. Audience(s): Customer, Partner, Developer Package (SQLServerBestPracticesPolicies.msi) Microsoft Windows PowerShell Extensions for SQL Server The Microsoft Windows PowerShell Extensions for SQL Server includes a provider and a set of cmdlets that enable administrators and developers to build PowerShell scripts for managing instances of SQL Server.
The SQL Server PowerShell Provider delivers a simple mechanism for navigating SQL Server instances that is similar to file system paths. PowerShell scripts can then use the SQL Server Management Objects to administer the instances. The SQL Server cmdlets support operations such as executing Transact-SQL scripts or evaluating SQL Server policies. Note: Windows PowerShell Extensions for SQL Server requires SQL Server 2008 Management Objects, also available on this page. This component also requires Windows PowerShell 1.0; download instructions are on the Windows Server 2003. Audience(s): Customer, Partner, Developer X86 Package (PowerShellTools.msi) X64 Package (PowerShellTools.msi) IA64 Package (PowerShellTools.msi) Microsoft SQL Server 2008 Replication Management Objects The Microsoft SQL Server 2008 Replication Management Objects package includes API for managing SQL Server 2008 replication objects programmatically.
The story of the show is a coming-of-age story that revolves around the protagonist, Arslaan, which is played. The serial premiered on 13th July, 2008 and ended on 19th October, 2008 after telecasting 15 episodes. The story is set three thousand years ago. Arslaan was Sony TV’s attempt at creating an identifiable superhero in Indian pop culture, but the serial was not successful in this attempt. Arslan sony tv drama. The serial was a weekly that used to air every Sunday at 7 at night.
The Replication Management Objects package requires Windows Installer 4.5, Microsoft SQL Server Native Client 10.0, and the SQL Server 2008 Management Objects (SMO) Collection package. Audience(s): Customer, Partner, Developer X86 Package (sqlrmo.msi) X64 Package (sqlrmo.msi) IA64 Package (sqlrmo.msi) Microsoft SQL Server 2008 Report Builder 2.0 Microsoft SQL Server 2008 Report Builder 2.0 provides an intuitive report authoring environment for business and power users with a Microsoft Office look and feel. Report Builder 2.0 supports the full capabilities of Report Definition Language (RDL) including flexible data layout, data visualizations, and richly formatted text features of SQL Server 2008 Reporting Services. The download provides a stand-alone installer for Report Builder 2.0. Note: This component also requires.
Audience(s): Customer, Partner, Developer Microsoft SQL Server 2008 Reporting Services Add-in for Microsoft SharePoint Technologies Microsoft SQL Server 2008 Reporting Services Add-in for SharePoint Technologies allows you to take advantage of SQL Server 2008 report processing and management capabilities in SharePoint integrated mode. This version also includes data-driven subscriptions. The download provides a Report Viewer Web part, Web application pages, and support for using standard Windows SharePoint Services or Microsoft Office SharePoint Services. Audience(s): Customer, Partner, Developer Microsoft SQL Service Broker External Activator The Microsoft SQL Service Broker External Activator is distributed in the Microsoft SQL Server 2008 Feature Pack. It is an extension of the Internal Activation feature in SQL Server 2008 and lets you move the logic for receiving and processing Service Broker messages from the Database Engine service to an application executable that runs outside the Database Engine service. This can provide a higher level of scale-out performance by moving processing loads from the database server to another computer.
![]()
The activation application process can also run under a different Windows account from the Database Engine process. This gives administrators additional control over the resources that the activation application can access. Run the self-extracting download package to create an installation folder. The single setup program will install the service on x86, x64, and IA64 computers.
Read the documentation for more information. Audience(s): Customer, Developer X86 Package(SSBEAS.msi) X64 Package (SSBEAS.msi) IA64 Package(SSBEAS.msi) Microsoft SQL Server System CLR Types The SQL Server System CLR Types package contains the components implementing the new geometry, geography, and hierarchyid types in SQL Server 2008. This component can be installed separately from the server to allow client applications to use these types outside of the server. Note: This component also requires.
Audience(s): Customer, Partner, Developer X86 Package(SQLSysClrTypes.msi) X64 Package (SQLSysClrTypes.msi) IA64 Package(SQLSysClrTypes.msi) Microsoft SQLXML 4.0 SP1 SQLXML enables XML support for your SQL Server Database. It allows developers to bridge the gap between XML and relational data. You can create XML View of your existing relational data and work with it as if it was an XML file. SQLXML allows you to:. Query relational database with XPath. Update relational data as if it was XML.
Load XML into SQL Server. Query SQL Server OLEDB/ADO or.NET Framework Managed Classes Microsoft SQLXML 4.0 SP1 provides support for new SQL Server 2008 data types such as Date, Time, DateTime2 and DateTimeOffset. Audience(s): Customer, Partner, Developer X86 Package(sqlxml.msi) X64 Package (sqlxml.msi) IA64 Package(sqlxml.msi) Microsoft Sync Framework Microsoft Sync Framework is a comprehensive synchronization platform that enables collaboration and offline access for applications, services and devices. Using the Microsoft Sync Framework runtime, developers can build sync ecosystems that integrate any application, with any data from any store using any protocol over any network.
Sync Services for ADO.NET is a part of the Microsoft Sync Framework. Sync Services for ADO.NET enables synchronization between ADO.NET enabled databases.
Because Sync Services for ADO.NET is part of the Microsoft Sync Framework, any database that uses Sync Services for ADO.NET can then also exchange information with other data sources that are supported by Microsoft Sync Framework, such as web services, file systems or custom data stores. For more information about the Microsoft Sync Framework, please go to.
Audience(s): Customer, Developer X86 Package(Synchronization.msi) X64 Package (Synchronization.msi) IA64 Package(Synchronization.msi) X86 Package(SyncServicesADO.msi) X64 Package (SyncServicesADO.msi) IA64 Package(SyncServicesADO.msi).
I have recently formatted my hard drive and over the past few days I've been reloading my software. I have installed on my machine SQL Server Express 2005 SP3. I prefer to have SQL Express running on my development machine because that is what my customers primarily use.
I also have a full MSDN license, and I would need to install SQL Management Studio 2005. However, when I download the SQL Server 2005 Developer ISO from MSDN, and run the setup file I get an error message that states: Installation of Microsoft SQL Server Native Client failed because a higher version already exists on the machine. To proceed, uninstall the higher version and then run Microsoft SQL Server Native Client Setup. I would assume the problem is that the copy of SQL Server - Dev Edition that is available through my MSDN subscription is using an earlier version of SQL Server 2005 (most likely the version prior to SP1.) I would just unistall SQL Server Express 2005 SP3 and reinstall it with out any service pack updates.
The problem is that I also see within my Add or Remove Programs list four SQL Server 2008 R2 entries, that I believe were installed when I installed Visual Studio Pro 2010 (they are, Microsoft SQL Server 2008 R2 Data-Tier Application Framework, Microsoft SQL Server 2008 R2 Data-Tier Application Project, Microsoft SQL Server 2008 R2 Managment Objects & Microsoft SQL Server 2008 R2 Transact-SQL Language Services) I have no idea of what those SQL 2008 entries are for and I'd rather not uninstall them if I will potentially be using them in future projects that I create in VS2010. I assume it is a possibility that they are clashing with my installation attempts, rather than my installation of SQL Express 2005 SP3 but I'm not sure. What I need is to be able to install some full version of SQL Management Studio 2005, while having any version of SQL Server Express 2005 on my machine. I have found in the past that SQL Server can start to act 'finicky' if you uninstall and reinstall a bunch of versions.
In fact, I had to reformat my HD because I could not install any version of SQL Server under a mandatory instance name. I have nothing against an un-installation and re-installation of software. My fear, though, is that lingering registry entries will prevent a clean, usable installation from taking place, especially when I specify a SQL Server instance ID that I had previously used. I've tried to swith SQL Server versions in this manner before and, well, it screwed the registry so badly I had to reformat the computer.
Expert comments are appreciated. I need assurance that this won't happen again but I understand that all suggestions are offered without warranty.:). Hi BMRH, First, you are right.
The error 'Installation of Microsoft SQL Server Native Client failed because a higher version already exists on the machine. To proceed, uninstall the higher version and then run Microsoft SQL Server Native Client Setup.' Is caused by the SQL Server Native Client that had been installed has a newer version than the one you want to install. SQL Server Native Client is a shared component of SQL Server. All instance in the same server will use only one copy of the shared components.
If a newer verison shared component is installed, we are not able to install another older version. In this case, to fix this issue, we can uninstall the shared components of SQL Server Express 2003, and then re-install the SQL Server Developer edition. After that, please apply the SP3 hotfix at least. By default, all related registry entries will be removed if we uninstall SQL Server. However, if we have met such issue(lingering registry entries ), we can backup the registry, and then remove the SQL Server related entries manually.
If there is anything unclear, please feel free to ask. Thanks, Jin Chen Jin Chen - MSFT. Hi BMRH, First, you are right. The error 'Installation of Microsoft SQL Server Native Client failed because a higher version already exists on the machine.
To proceed, uninstall the higher version and then run Microsoft SQL Server Native Client Setup.' Is caused by the SQL Server Native Client that had been installed has a newer version than the one you want to install.
SQL Server Native Client is a shared component of SQL Server. All instance in the same server will use only one copy of the shared components. If a newer verison shared component is installed, we are not able to install another older version. In this case, to fix this issue, we can uninstall the shared components of SQL Server Express 2003, and then re-install the SQL Server Developer edition. After that, please apply the SP3 hotfix at least. By default, all related registry entries will be removed if we uninstall SQL Server.
However, if we have met such issue(lingering registry entries ), we can backup the registry, and then remove the SQL Server related entries manually. If there is anything unclear, please feel free to ask. Thanks, Jin Chen Jin Chen - MSFT.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |