Feb 16, 2014 I was trying to install report viewer and required Microsoft system CLR types for SQL server 2012 on a server 2012 r2 where SQL server 2012 SP1 already installed with. The Microsoft® SQL Server® 2012 Native Client is available as part of Microsoft® SQL Server® 2012 Feature Pack, which is updated at each SQL Server 2012 Service Pack. This download is the latest cumulative servicing (QFE) update made to the most recent 2012 Feature Pack release of the SQL Server® 2012 Native Client.
-->AdventureWorks download links and installation instructions.
Ms Sql Server 2012 Download Free
Prerequisites
- SQL Server or Azure SQL Database. For the Full version of the sample, use SQL Server Evaluation/Developer/Enterprise Edition.
- SQL Server Management Studio. For the best results use the June 2016 release or later.
Github links
![Microsoft sql server 2012 download for windows 7 Microsoft sql server 2012 download for windows 7](/uploads/1/2/6/4/126427721/976203873.jpg)
OLTP downloads
Direct links to the OLTP versions of AdventureWorks can be found below:
Data Warehouse downloads
Direct links to the Data Warehouse versions of AdventureWorks can be found below:
Creation scripts
The below scripts can be used to create the entire AdventureWorks database, irrespective of version.
Install to SQL Server
Restore backup
Follow the below steps to restore a backup of your database using SQL Server Management Studio.
- Open SQL Server Management Studio and connect to the target SQL Server instance.
- Right-click on the Databases node, and select Restore Database.
- Select Device and click the ellipses (...)
- In the dialog Select backup devices, click Add, navigate to the database backup in the filesystem of the server, and select the backup. Click OK.
- If needed, change the target location for the data and log files, in the Files pane. Note that it is best practice to place data and log files on different drives.
- Click OK. This will initiate the database restore. After it completes, you will have the AdventureWorks database installed on your SQL Server instance.
For more information on restoring a SQL Server database, see Restore a database backup using SSMS.
Attach a datafile
Follow the below steps to attach the datafile for your database using SQL Server Management Studio.
- Open SQL Server Management Studio and connect to the target SQL Server instance.
- Right-click on the Databases node, and select Attach.
- Select Add and navigate to the .MDF file you want to attach.
- Select the file and click OK.
- The database you selected should be displayed in the bottom window. If the file is listed as 'not found', select the ellipses (...) next to the file name and update the path to the correct path.
- If you only have the data file (.mdf), and not the log file (.ldf), then highlight the .ldf in the bottom window and select Remove. This will create a new log file.
- Select OK to attach the file. After the file is attached, you will have the AdventureWorks database installed on your SQL Server instance.
For more information on attaching database files, see Attach a database.
Install to Azure SQL Database
If you do not yet have a SQL Server in Azure, navigate to the Azure portal and create a new SQL Database. In the process of create a database, you will create a server. Make note of the server. See this tutorial to create a database in minutes.
- Connect to your Azure portal.
- Select Create a resource in the top left of the navigation pane.
- Select Databases and then select SQL Database.
- Fill in the requested information.
- In the Select Source field, select Sample (AdventureWorksLT) to restore a backup of the latest AdventureWorksLT backup.
- Select Create to create your new SQL Database, which is the restored copy of the AdventureWorksLT database.
See also
Tutorials for SQL Server Management Studio
Tutorials for SQL Server database engine
-->Tutorials for SQL Server database engine
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. For more information, see SQL Server Native Client.
You can also get sqlncli.msi from the SQL Server 2012 Feature Pack web page. To download the most recent version of the SQL Server Native Client, go to Microsoft速 SQL Server速 2012 Feature Pack. 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 s11ch_sqlncli.chm) are installed to the following location:
%SYSTEMROOT%system32
Note
All appropriate registry settings for the SQL Server Native Client OLE DB provider and the SQL Server Native Client ODBC driver are made as part of the installation process.
The SQL Server Native Client header and library files (sqlncli.h and sqlncli11.lib) are installed in the following location:
%PROGRAMFILES%Microsoft SQL Server110SDK
In addition to installing SQL Server Native Client as part of the SQL Server installation, there is also a redistributable installation program named sqlncli.msi, which can be found on the SQL Server installation disk in the following location:
%CD%Setup
.You can distribute SQL Server Native Client through sqlncli.msi. You might have to install SQL Server Native Client when you deploy an application. One way to install multiple packages in what seems to the user to be a single installation is to use chainer and bootstrapper technology. For more information, see Authoring a Custom Bootstrapper Package for Visual Studio 2005 and Adding Custom Prerequisites.
The x64 and Itanium versions of sqlncli.msi also install the 32-bit version of SQL Server Native Client. If your application targets a platform other than the one it was developed on, you can download versions of sqlncli.msi for x64, Itanium, and x86 from the Microsoft Download Center.
When you invoke sqlncli.msi, only the client components are installed by default. The client components are files that support running an application that was developed using SQL Server Native Client. To also install the SDK components, specify
ADDLOCAL=All
on the command line. For example:msiexec /i sqlncli.msi ADDLOCAL=ALL APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
Silent Install
If you use the /passive, /qn, /qb, or /qr option with msiexec, you must also specify IACCEPTSQLNCLILICENSETERMS=YES, to explicitly indicate that you accept the terms of the end user license. This option must be specified in all capital letters.
Uninstalling SQL Server Native Client
Because applications such as SQL Server server and the SQL Server tools depend on SQL Server Native Client, it is important not to uninstall SQL Server Native Client until all dependent applications are uninstalled. To provider users with a warning that your application depends on SQL Server Native Client, use the APPGUID install option in your MSI, as follows:
msiexec /i sqlncli.msi APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
The value passed to APPGUID is your specific product code. A product code must be created when using Microsoft Installer to bundle your application setup program.
See Also
Building Applications with SQL Server Native Client
Installation How-to Topics
Installation How-to Topics