Sql server 2018 скачать для windows 10

Download links and complete information for all Microsoft SQL Server versions and builds

Headers:

• Frequently used terms and acronyms
• SQL Server Patching Shortcut
• What are the most recent updates for SQL Server?
• Microsoft SQL Server installation files info
• SQL Server Developer Edition Info
• SQL Server Express direct download links
• Internal Database Version and Compatibility Level
• Microsoft SQL Server 2019 Builds
• Microsoft SQL Server 2017 Builds
• Microsoft SQL Server 2016 Builds
• Microsoft SQL Server 2014 Builds
• Microsoft SQL Server 2012 Builds
• Microsoft SQL Server 2008 R2 Builds
• Microsoft SQL Server 2008 Builds
• Microsoft SQL Server 2005 Builds
• Microsoft SQL Server 2000 Builds
• Microsoft SQL Server 7.0 Builds
• Microsoft SQL Server 6.5 Builds
• Microsoft SQL Server 6.0 Builds

Useful links:

• KB321185 How to determine the version, edition and update level of SQL Server and its components
• KB822499 Naming schema for Microsoft SQL Server software update packages
• Microsoft SQL Server Support Lifecycle
• Microsoft Update Catalog
• SQL Server packages for Linux
• Release notes for SQL Server 2017 on Linux
• KB824684 Description of the standard terminology that is used to describe Microsoft software updates
• KB935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
• KB2964518 Recommended updates and configuration options for SQL Server 2012 and SQL Server 2014 with high-performance workloads
• Azure SQL Server Updates
• Most Recent KBs for Microsoft SQL Server RSS
• Testing and Developing Supportability Roadmaps for ISV Applications (PDF)
• SQL Server Updates by Brent Ozar team
• Which Version of SQL Server Should You Use?
• SQL Server Builds by SQLSentry
• SQL Server Builds by SQLPerformance.com
• SQL Server Release Services
• Why I have high hopes for the quality of SQL Server 2016 release by Remus Rusanu
• Unofficial SQL Server build chart lists
• Unofficial SQL Server build chart lists in table representation
• Hardware and Software Requirements for Installing SQL Server
• Wikipedia Microsoft SQL Server
• SQL Server 2005 Downloads
• SQL Server 2000 Downloads
• SQL Server 7.0 Downloads

Useful articles:

• How to identify your SQL Server version and edition
• SQL Server Internal Database Versions
• Microsoft SQL Server Support Lifecycle
• Microsoft SQL Server Home
• Microsoft SQL Server Developer Center
• Microsoft TechNet: Microsoft SQL Server
• SQL Server Patching Shortcut

All SQL Server service packs and Cumulative Updates are cumulative, meaning that each new service pack and cumulative update contains all the fixes that are included with previous service packs and any new fixes.

Frequently used terms and acronyms

Great thanks to Aaron Bertrand for awesome article: Definitions of SQL Server release acronyms

• COD Critical On-Demand: This is a fix for an issue that is deemed «critical» because of the severity of the issue, the number of customers it affects,
  or the lack of a feasible workaround (usually a combination of two or all three).
  The fix is released out-of-band from the usual Cumulative Update / Service Pack release cycle, and then rolled into the next Cumulative Update (or, depending on timing, the one after that).
  A COD can sometimes contain more than one QFE (defined below).
• CU Cumulative Update: This is a roll-up of multiple fixes that occurs between Service Packs, usually on a 60-day cycle (though that is subject to change).
  It used to require an e-mail and password to download and extract the files, because they were «less tested» than service packs, but this is no longer the case.
  Functionality can also be added in Cumulative Updates (previously, this would only happen in Service Packs, and before that, only in major releases).
  Kendra Little just published a fantastic blog post about this.
  You should feel comfortable applying Cumulative Updates as quickly as your regression and other test processes allow.
• CTP Community Technology Preview: This is a build of the «next» version of SQL Server (or sometimes a Service Pack) that can be used for testing new features and reporting bugs.
  With few exceptions, CTPs cannot be used in a production scenario, and they are usually limited to Express / Evaluation Editions.
• GA General Availability: For the traditional SQL Server product, this usually means that you can download the ISO from the usual sources (MSDN downloads, the TechNet Evaluation Center, or your volume licensing servers).
  For Azure SQL Database, this usually means that you can go and turn on the functionality without first agreeing to a waiver about preview functionality.
• GDR General Distribution Release: A GDR fix contains issues that are security-related and/or have a wide impact, and are released without any other critical updates that have been released for the specific branch.
  These are typically used by customers who need the fixes they contain, but do not have the resources to test all of the other fixes that come with Cumulative Updates.
• QFE Quick Fix Engineering: This is a potentially less-tested fix (also sometimes called a hotfix) that gets distributed to a small number of customers for a very specific issue, through a COD or CU.
  (In the Windows world, this is called an LDR – Limited Distribution Release – but that nomenclature has not caught on in the SQL Server team.)
• RC Release Candidate: This is a build that is almost ready for final release (RTM / GA). Usually it is feature complete, with the only remaining work comprised of minor bug fixes and fit & finish.
  However, this is not always strictly the case, as a few behavior changes were introduced in RCs for SQL Server 2016.
• RDP Rapid Deployment Program: No, this has nothing to do with remote desktop; it refers to a set of «early adopter» customers, usually used to help market the launch of a new version or feature.
  These are almost always a subset of TAP, and are almost always running the new version in production months before it is available to the public. James Serra goes into more detail here.
• RTM Released To Manufacturing: This means that the release is ready. Back when Microsoft shipped software on CDs and later DVDs, this represented the point in time when the discs could be printed.
  Not to be confused with launch (which is a marketing thing only) or General Availability (which means you can actually get the code).
  The delay between RTM and GA is much shorter now that software is generally distributed online instead of on physical media.
• RTW Release to Web: It indicates a package that was released to the web and made available to customers for downloading.
• TAP Technology Adoption Program: This describes a set of customers that help Microsoft shape and test specific features for a new release (or help shape and test new features individually).
• SP Service Pack: A Service Pack is, now, essentially a Cumulative Update with slightly different labeling.
  It is a roll-up of updates (including bug fixes and security updates) and sometimes contains new features.
  Like Cumulative Updates, Service Packs are cumulative. If you are applying SP3, you do not need to first deploy SP1 and SP2.
• SU or CVE: Security update.
• Hotfix: A single, cumulative package that includes one or more files that are used to address a problem in a product and are cumulative at the binary and file level. A hotfix addresses a specific customer situation and may not be distributed outside the customers organization.

References

• KB #824684 : Description of the standard terminology that is used to describe Microsoft software updates
• KB #935897 : An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
• QFE vs GDR/LDR hotfixes
• GDR, QFE, LDR… WTH?
• GDR & LDR : The Next Generation
• Terms used by Microsoft to describe the various software updates released by it
• What is Microsoft TAP and RDP?

SQL Server Patching Shortcut

Step 1. After the CU file has been downloaded, open a DOS prompt and launch it with the /extract option with a path of your choice appended to this option. For example:

SQLServer2017-KB4052574-x64.exe /extract C:SQL2017CU2

After a few moments you should see the progress bar dialog pop up. The target directory will be created if it does not exist, so this is also a great option for automating patch installs.

No step 2 required. The patch has been extracted to a location of your choice, which means there’s one less thing to worry about when it’s time to carry out the actual patching.

Profits:

• This saves time as the install files can be extracted in advance, and if you have to patch a lot of servers this saving is multiplied as the files are extracted once, instead of every time on every server.
• This time saving also serves to reduces risk as it is one less thing that could go wrong during patching. The last thing you want to be doing during a patching window is scrambling around on a server clearing space in temp folders because there was not enough space free on e.g. the C: drive for the patch to extract itself.
• This is also a great way of retrieving just an individual msi file (e.g. sqlncli.msi)

What are the most recent updates for SQL Server?

Microsoft SQL Server installation files info

SHA1 hash you can easy get with default Windows utility certutil.

For example, for single file:

certUtil -hashfile "d:SQL ServerSQLServer2014SP1-KB3058865-x64-ENU.exe" sha1

Or for all files with .exe extensions in folder:

FOR /R "d:SQL Server" %I IN (*.exe) DO certUtil -hashfile "%I" sha1

Alternative download link for all English x64 distributives: https://rebrand.ly/sql-server-distribs

For downloading distributive for SQL Server 2008 R2 and SQL Server 2008 you must have MSDN subscription, see SQL Server 2008 R2 and SQL Server 2008 links.

SQL Server Developer Edition Info

Now it is free!!! SQL Server Developer Edition Download page

For downloading your copy SQL Server Developer Edition you just need to join the Visual Studio Dev Essentials program

SQL Server Express direct download links

Original post written by Scott Hanselman: http://www.hanselman.com/blog/DownloadSQLServerExpress.aspx
Official Microsoft SQL Server Express page: https://www.microsoft.com/server-cloud/products/sql-server-editions/sql-server-express.aspx

Download SQL Server 2017 Express

Download SQL Server 2016 Express

Download SQL Server 2014 Express

Download Microsoft SQL Server 2014 Service Pack 1 (SP1) Express
You likely just want SQL Server 2014 Express with Tools. This download includes SQL Management Studio:

• SQL Server 2014 Express x64
• SQL Server 2014 Express x86

Here’s just SQL Server 2014 Management Studio:

• SQL Management Studio x64
• SQL Management Studio x86

SQL Server 2014 Express with Advanced Services:

• Advanced Services x64
• Advanced Services x86

Download SQL Server 2012 Express

Download Microsoft SQL Server 2012 Service Pack 1 (SP1) Express
You likely just want SQL Server 2012 Express with Tools. This download includes SQL Management Studio:

• SQL Server 2012 Express x64

Here’s just SQL Server 2012 Management Studio:

• SQL Management Studio x64
• SQL Management Studio x86

Download SQL Server 2008 Express R2 SP2

You likely just want SQL Server 2008 Express with Tools. This download includes SQL Management Studio:

• SQL Server 2008 Express x64
• SQL Server 2008 Express x86

Here’s just SQL Server 2008 Management Studio:

• SQL Management Studio x64
• SQL Management Studio x86

Download SQL Server 2005 Express

Internal Database Version and Compatibility Level

Database Compatibility Level

The compatibility level of a database dictates how certain language elements of the database function as it relates to an earlier version of SQL Server.
In a nutshell, this offers up partial “backward compatibility” to an earlier version.
This functionality is not all encompassing as only certain aspects (i.e. certain syntax) of the database would pertain to this setting.

You can see what compatibility level a database is at by using the SSMS or via code.

Via SSMS:

1. After connecting to the appropriate instance of the SQL Server Database Engine, in Object Explorer, click the server name.
2. Expand Databases, and, depending on the database, either select a user database or expand System Databases and select a system database.
3. Right-click the database, and then click Properties. The Database Properties dialog box opens.
4. In the Select a page pane, click Options. The current compatibility level is displayed in the Compatibility level list box.
5. To change the compatibility level, select a different option from the list. The choices are SQL Server 2008 (100), SQL Server 2012 (110) or SQL Server 2014 (120).

Via T-SQL:

-- For SQL Server 2005 and newer
SELECT name, compatibility_level FROM sys.databases WHERE name = 'DatabaseNameHere';

-- For SQL Server 2000
SELECT name, cmptlevel FROM sysdatabases WHERE name = 'DatabaseNameHere';

To ALTER DATABASE Compatibility Level use simple command:

ALTER DATABASE database_name SET COMPATIBILITY_LEVEL = { 150 | 140 | 130 | 120 | 110 | 100 | 90 }

Internal Database Version and Compatibility level

The Importance of Database Compatibility Level in SQL Server

The database version is a number stamped in the boot page of a database that indicates the SQL Server version of the most recent SQL Server instance the database was attached to.
The database version number does not equal the SQL Server version and does not equal the compatibility level should be considered as a completely different attribute of the database.

The database version is an internal versioning system that defines what version of SQL Server the database was a recent resident of.
If you migrate a database from an older version to a newer version, the database version value will be increased to reflect the version number of the new server’s model database.

When you create a database, the database version is «stamped» with the same version as the Model database.
It is worth noting that if the Model database was originally created on a different server edition and then subsequently upgraded, you potentially could end up
with slightly different numbers than what you might expect.
As you upgrade the database to new SQL Server edition (you can not go backward) the version of the database increases.
This is done automatically regardless of what method you use to upgrade the database to the new version of SQL Server.

/* 1 using DBCC PAGE to look at the boot page (9) of the database
Search dbi_version string
 */
DBCC TRACEON(3604);
DBCC PAGE('DatabaseName', 1, 9, 3);
DBCC TRACEOFF(3604);
GO

/* 2 using DBCC DBINFO */
DBCC TRACEON(3604);
DBCC DBINFO;
DBCC TRACEOFF(3604);
GO

/* 3 using database property */
SELECT DatabaseProperty('DatabaseNameHere', 'version');
GO

/* 4 using RESTORE HEADERONLY for backup files, field DatabaseVersion */
RESTORE HEADERONLY FROM DISK=N'd:DatabseBackupFile.bak' WITH NOUNLOAD;
GO

You will note that for each DBCC command we have to turn on trace flag 3604 so that the output of the DBCC command is sent to the SSMS window rather than the default location, the SQL Server log.

If you are still on SQL Serever 2000, you can see this information with a simple query:

SELECT name, version FROM master.dbo.sysdatabases;

Execute the following query to determine the version of the Database Engine that you are connected to:

SELECT SERVERPROPERTY('ProductVersion');

Azure SQL Database V12 was released in December 2014. One aspect of that release was that newly created databases had their compatibility level set to 120. In 2015 SQL Database began support for level 130, although the default remained 120.

Starting in mid-June 2016, in Azure SQL Database, the default compatibility level will be 130 instead of 120 for newly created databases. Existing databases created before mid-June 2016 will not be affected, and will maintain their current compatibility level (100, 110, or 120).

If you want level 130 for your database generally, but you have reason to prefer the level 110 cardinality estimation algorithm, see ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL), and in particular its keyword LEGACY_CARDINALITY_ESTIMATION =ON.

For details about how to assess the performance differences of your most important queries, between two compatibility levels on Azure SQL Database, see Improved Query Performance with Compatibility Level 130 in Azure SQL Database.

References

• Compatibility Level vs Database Version (by John Morehouse)
• What’s the difference between database version and database compatibility level? (by Paul Randal)
• ALTER DATABASE Compatibility Level (Transact-SQL)
• View or Change the Compatibility Level of a Database
• Database Version vs Database Compatibility Level (by Jonathan Kehayias)

Microsoft SQL Server 2019 Builds

More additional information about latest vNext SQL Server release you can find in this articles:

• What’s new in SQL Server 2019
• What’s New in the First Public CTP of SQL Server 2019
• Froid: How SQL Server vNext Might Fix the Scalar Functions Problem
• What’s New in SQL Server 2019 System Tables
• What’s New in SQL Server 2019’s sys.messages: More Unannounced Features
• What’s New in SQL Server 2019: Faster Table Variables (And New Parameter Sniffing Issues)
• What’s New in SQL Server 2019: Adaptive Memory Grants
• Leaked: SQL Server 2019 Big Data Clusters Introduction Video
• Native UTF-8 Support in SQL Server 2019: Savior, False Prophet, or Both?

Here is the latest output from SELECT @@VERSION for SQL Server 2019 CTP Developer Edition:

Microsoft SQL Server 2019 (RTM-CU2) (KB4536075) - 15.0.4013.40 (X64) 
   Feb  3 2020 16:40:57 
   Copyright (C) 2019 Microsoft Corporation
   Developer Edition (64-bit) on …

Microsoft SQL Server 2017 Builds

All SQL Server 2017 CU downloads: Catalog Update Microsoft SQL Server 2017

Here is the latest output from SELECT @@VERSION for SQL Server 2017 Developer Edition:

Microsoft SQL Server 2017 (RTM-CU19) (KB4535007) - 14.0.3281.6 (X64) 
   Jan 23 2020 21:00:04 
   Copyright (C) 2017 Microsoft Corporation
   Developer Edition (64-bit) …

Microsoft SQL Server 2016 Builds

All SQL Server 2016 CU downloads: Catalog Update Microsoft SQL Server 2016

Here is the latest output from SELECT @@VERSION for SQL Server 2016 Developer Edition on Windows:

Microsoft SQL Server 2016 (SP2-CU11) (KB4527378) - 13.0.5598.27 (X64)
   Nov 28 2019 00:04:50
   Copyright (c) Microsoft Corporation
   Developer Edition (64-bit) on …

Microsoft SQL Server 2014 Builds

All SQL Server 2014 CU downloads: Catalog Update Microsoft SQL Server 2014

Here is the latest output from SELECT @@VERSION for SQL Server 2014 Developer Edition on Windows:

Microsoft SQL Server 2014 (SP3-CU4) (KB4500181) - 12.0.6329.1 (X64)
   Jul 20 2019 21:42:29
   Copyright (c) Microsoft Corporation
   Developer Edition (64-bit) on …

Microsoft SQL Server 2012 Builds

All SQL Server 2012 CU downloads: Catalog Update Microsoft SQL Server 2012

Microsoft SQL Server 2008 R2 Builds

All SQL Server 2008 R2 CU downloads

Microsoft SQL Server 2008 Builds

Microsoft SQL Server 2005 Builds

Microsoft SQL Server 2000 Builds