SQL Server / Minimum OS Software Requirement

Background

Wanted to tabulate the minimum MS Windows OS Requirement for the various versions of MS SQL Server.

 

Minimum OS Support Matrix

SQL Server Version OS Version – Server OS Version – Desktop Bitness Link
v2017  Windows Server 2012  Windows 8 Minimum: x64 Processor: 1.4 GHz
Recommended: 2.0 GHz or fasterDoes not support 32 bit OS
 Link
v2016  Windows Server 2012  Windows 8 Minimum: x64 Processor: 1.4 GHz
Recommended: 2.0 GHz or fasterDoes not support 32 bit OS
 Link
v2014  Windows Server 2008  Windows 7  x64 Processor
x86 Processor
 Link
v2012  Windows Server 2008  Windows Vista x86 Processor: 1.0 GHz
x64 Processor: 1.4 GHz
 Link
v2008-R2  Windows Server 2003 Windows Vista
Windows XP
x64 Processor
x86 Processor
 Link
v2008  Windows Server 2003 Windows Vista
Windows XP
x64 Processor
x86 Processor
 Link
 v2005  Windows Server 2000  Windows Vista
Windows XP
600-megahertz (MHz) Pentium III-compatible or faster processor
1-gigahertz (GHz) or faster processor recommended
 Link

 Link

 v2000  Windows NT Server 4.0  Windows 98
Link
 

 

 

SQL Server 2017 – Developer Edition – ISO

Background

Currently, I have SQL Server 2014 Developer Edition on my laptop.

Recently found out that since my machine is now Windows 10, I can have SQL Server 2017 Developer Edition.

 

Download ISO

Let us go download v2017 Developer Edition.

v2017 is available here.

Available

Image

Textual

  1. Free Trial Evaluation
  2. Developer edition
  3. Express edition

Developer Edition

If we click on the “Download now” button underneath the “Developer edition“, we will notice that the name of the file that will be availed is SQLServer2017-SSEI-Dev.exe.

Already have that file and it is a small file.

I don’t really want a small file, I want the full ISO.

 

Self-Prepare ISO

Download Bootstrap

To get a nice ISO, please process with downloading SQLServer2017-SSEI-Dev.exe.

 

Prepare ISO

Outline

  1. Select an installation type
  2. Specify SQL Server Installer download
    • Which package will you like to download
      • ISO
      • CAB
    • Click on the Browser folder button
      • Choose an existing folder or create a new folder
      • Click the OK button
    • Click the OK button
  3. Download Media

Screen shot

Select an Installation Type

 

Specify SQL Server Installer download

Browse Folder

Download Media

Download Successful

 

Installed

Once the files was packaged into a nice ISO, was able to install it.

 

Conclusion

So unfortunately, it appears that one cannot download v2017 as a nice offline ISO.

But, please do not let that overly deter you.

Go ahead and download SQLServer2017-SSEI-Dev.exe and run it.

You will be able to prepare an ISO through running that package.

SQL Server – Upgrade – “It is not possible to change the SQL Server features to be upgraded in this release”

Background

Trying to upgrade the SQL Server Instance, but kept shooting blanks.

 

Blanks

SQL Server v2005 to v2014

Upgrade to SQL Server 2014

Shared Features

Textual

It is not possible to change the SQL Server features to be upgrade in this release.

Image

Select Features

Textual

There are validation errors on this page.  Click OK to close this dialog box. Review errors at the bottom of the error page, then provide valid parameters or click Help for information.

There are no features selected for upgrade.

TroubleShooting

Looked everywhere on this one.

But, then thought back to a few months past.

 

SQL Server Instance

Version Info

SQL


select @@version

Output

Image

Textual

Microsoft SQL Server 2005 – 9.00.5000.00 ( Intel X86 )
Dec 10 2010 10:56:29
Express Edition on Windows NT 6.1 ( Build 7601: Service Pack 1)

 

Tabulate

  1. Version :-
    • We are running Microsoft SQL Server v2005
  2. Platform :- Intel x86
  3. Edition :- Express Edition
  4. OS :- Windows NT 6.1 ( Build 7601 : Service Pack 1 )
    • MS Windows 2008/R2
    • Service Pack 1

 

32 Bit?

It appears that we are running 32-bit SQL Server

Control Panel

Services
Image

Textual
  1. path to executable :- C:\Program Files (x86) \XDM-SQLExpress\MSSQL.1\MSSQL\Binn\sqlservr

 

Explorer

Folder :- C:\Program files (x86) \ XDM-SQLExpress – MSSQL.1 \ MSSQL \ Data
Image

Explanation

Confirmed that our files are in the “C:\Program Files x86” folder

Remediation

  1. Prepare to re-Install
    • Preserve SQL Server data and log files
      • Take SQL Server Services offline and copy files over to safe location
      • Backup databases
    • Capture SQL Server Logins
  2. Uninstall Microsoft SQL Server v2005
  3. Install Microsoft SQL Server v2014
    • Our OS, MS Windows 2008-R2, only let us go up v2014
    • Apply MS SQL Server v2014 – SP2 and Cumulative Updates
  4. Restore
    • Re-create SQL Server Logins
    • Re-attach data & log files

Summary

Sometimes simple SQL Server Upgrades take on a life of their own.

SQL Server (v2016) – Installation – Blocked – “Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase”

Background

In the process of installing “SQL Server 2016” for a new client.

As it is a new client and not really sure exact features they will be using, chose to install “All features“.

Install Blocked

Installation is blocked with the error pasted below:

ScreenShot

Feature Rules

Image

Text

Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase.

Rule Check Result

Image

Text

This computer does not have the Oracle Java SE Runtime Environment Version 7 Update 51 (64-bit) or higher installed.  The Oracle Java SE runtime environment is software provided by a third-party software.

To continue, download the Oracle SE Java Runtime Environment from http://go.microsoft.com/fwlink/?LinkId=526030.

 

 

Remediation

Visited Microsoft URL

Visited the listed Microsoft page and directed right away to Oracle’s Java download page.

 

Java Standard Edition Downloads

Here are the downloads available for java Standard Edition ( Java SE)

 

Explanation

  1. JDK
    • We know we need JRE ( Java Runtime Engine), and not JDK ( Java Development Kit )
  2. Server JRE
    • Thought we could get away with the the lighter footprint Server JRE
  3. JRE
    • JRE

 

Server JRE

Server JRE – Downloads

Chose Windows x64.

Install Package Contents

The installer is bundled as a tar.gz.

Using 7-Zip extracted the file, but no installer.

Just app executable and class files.

Need more than that to install JRE and have SQL recognize that Java JRE is installed.

 

JRE

Java SE Runtime Environment 8 Downloads

Needed an executable offline installer and our bitness is 64 bit and so chose jre-8u131-windows-x64.exe.

 

Install

Actual Installation is straightforward.

ScreenShot

Welcome

 

Destination Folder

Create destination Folder beforehand.

Here is a sample script.


@echo off
rem _folder=C:\Program Files\java\jre1.8.0_131
set "_folder=E:\ProgramFiles\Java\JRE1.8.0_131"

if not exist %_folder% mkdir %_folder%

 

 

 

Destination Folder ( Changed )

 

Java Setup – Progress

 

Java Setup – Complete

Summary

If you will be evaluating \ using Polybase as part of SQL Server v2016, please download and install Oracle JRE ( Java Runtime engine) beforehand.

For JRE, there are two packages available for download.  One is marked Server and the generic one.

Please choose the generic, full version.

SQL Server 2012 – Install Failed – SQLWriter Service Disabled

Background

Trying to install a named instance to a machine with a default installed, but failed.

 

Error Messages

Detail.txt

Image

Textual


(01) 2017-05-01 08:22:03 Slp: Sco: Returning service process id 1468
(01) 2017-05-01 08:22:03 SQLEngine: : Checking Engine checkpoint 'GetSqlServerProcessHandle_2'
(01) 2017-05-01 08:22:03 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$PERF' to be created
(01) 2017-05-01 08:22:04 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$PERF' or sql process handle to be signaled
(01) 2017-05-01 08:22:04 SQLEngine: : Checking Engine checkpoint 'WaitSqlServerStartEvents_1'
(01) 2017-05-01 08:22:04 SQLEngine: --SqlServerServiceSCM: Starting dependents of service 'MSSQL$PERF' in opposite order ...
(01) 2017-05-01 08:22:04 SQLEngine: Copying 'D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log\ERRORLOG' to 'C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20170501_080639\SQLServer_ERRORLOG_2017-05-01T08.22.04.txt' ...
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to copy file 'D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log\ERRORLOG' to file 'C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20170501_080639\SQLServer_ERRORLOG_2017-05-01T08.22.04.txt'
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to get security descriptor for file 'D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log\ERRORLOG'
(01) 2017-05-01 08:22:04 Slp: Sco: Returning security descriptor O:S-1-5-80-1696324543-2353754024-1556012342-4066776139-377137144G:S-1-5-80-1696324543-2353754024-1556012342-4066776139-377137144D:AI(A;ID;FA;;;S-1-5-80-1696324543-2353754024-1556012342-4066776139-377137144)(A;ID;FA;;;SY)(A;ID;FA;;;BA)(A;ID;0x1201ff;;;S-1-5-80-2284653297-3842300192-3001888380-618865920-1741683089)
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to get files for directory D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log, search pattern SQLDump*.mdmp
(01) 2017-05-01 08:22:04 SQLEngine: Copy '0' mdmp files from 'D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log' to 'C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20170501_080639' ...
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to get files for directory D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log, search pattern *.xel
(01) 2017-05-01 08:22:04 SQLEngine: "xel" file 'C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20170501_080639\system_health_0_131381257125540000_2017-05-01T08.21.52.xel' exists...
(01) 2017-05-01 08:22:04 Slp: Sco: File 'C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20170501_080639\system_health_0_131381257243270000_2017-05-01T08.22.04.xel' does not exist
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to copy file 'D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log\system_health_0_131381257243270000.xel' to file 'C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20170501_080639\system_health_0_131381257243270000_2017-05-01T08.22.04.xel'
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to get security descriptor for file 'D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log\system_health_0_131381257243270000.xel'
(01) 2017-05-01 08:22:04 Slp: Sco: Returning security descriptor O:S-1-5-80-1696324543-2353754024-1556012342-4066776139-377137144G:S-1-5-80-1696324543-2353754024-1556012342-4066776139-377137144D:AI(A;ID;FA;;;S-1-5-80-1696324543-2353754024-1556012342-4066776139-377137144)(A;ID;FA;;;SY)(A;ID;FA;;;BA)(A;ID;0x1201ff;;;S-1-5-80-2284653297-3842300192-3001888380-618865920-1741683089)
(01) 2017-05-01 08:22:04 SQLEngine: Copying 'D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log\system_health_0_131381257243270000.xel' to 'C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20170501_080639\system_health_0_131381257243270000_2017-05-01T08.22.04.xel' ...
(01) 2017-05-01 08:22:04 SQLEngine: Copy '1' xel files from 'D:\Program Files\Microsoft SQL Server\MSSQL12.PERF\MSSQL\Log' to 'C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20170501_080639' ...
(01) 2017-05-01 08:22:04 SQLEngine: : SQLWriter: Enabling Writer SID before starting it.
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to set service sid type for service SQLWriter, serivce sid type SERVICE_SID_TYPE_UNRESTRICTED
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to open SC Manager
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to open service handle for service SQLWriter
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to close service handle for service SQLWriter
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to close SC Manager
(01) 2017-05-01 08:22:04 SQLEngine: : SQLWriter: Starting Writer Service.
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to start service SQLWriter
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to open SC Manager
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to open service handle for service SQLWriter
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to close service handle for service SQLWriter
(01) 2017-05-01 08:22:04 Slp: Sco: Attempting to close SC Manager
(01) 2017-05-01 08:22:04 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing Startup and scenario Startup.
(01) 2017-05-01 08:22:04 Slp: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

(01) 2017-05-01 08:22:04 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2017-05-01 08:22:04 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing Startup and scenario Startup.
(01) 2017-05-01 08:22:04 Slp: System.ComponentModel.Win32Exception: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
(01) 2017-05-01 08:22:04 Slp:    at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams)
(01) 2017-05-01 08:22:04 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SQLWriterStarter.NetStartSQLWriterService(ServiceContainer context)
(01) 2017-05-01 08:22:04 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2017-05-01 08:22:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2017-05-01 08:22:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2017-05-01 08:22:04 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2017-05-01 08:22:04 Slp: Inner exceptions are being indented
(01) 2017-05-01 08:22:04 Slp: 
(01) 2017-05-01 08:22:04 Slp: Exception type: System.ComponentModel.Win32Exception
(01) 2017-05-01 08:22:04 Slp:     Message: 
(01) 2017-05-01 08:22:04 Slp:         The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
(01) 2017-05-01 08:22:04 Slp:         
(01) 2017-05-01 08:22:04 Slp:     HResult : 0x80004005
(01) 2017-05-01 08:22:04 Slp:     Error : 1058
(01) 2017-05-01 08:22:04 Slp:     Data: 
(01) 2017-05-01 08:22:04 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2017-05-01 08:22:04 Slp:       WatsonConfigActionData = INSTALL@STARTUP@SQL_ENGINE_CORE_INST
(01) 2017-05-01 08:22:04 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2017-05-01 08:22:04 Slp:     Stack: 
(01) 2017-05-01 08:22:04 Slp:         at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams)
(01) 2017-05-01 08:22:04 Slp:         at Microsoft.SqlServer.Configuration.SqlEngine.SQLWriterStarter.NetStartSQLWriterService(ServiceContainer context)
(01) 2017-05-01 08:22:04 Slp:         at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2017-05-01 08:22:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2017-05-01 08:22:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2017-05-01 08:22:04 Slp: Watson Bucket 1 
 Original Parameter Values 

(01) 2017-05-01 08:22:04 Slp: Parameter 0 : SQL Server 2014@RTM@ 

(01) 2017-05-01 08:22:04 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.Sco.Service.StartService 

(01) 2017-05-01 08:22:04 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.Service.StartService 

(01) 2017-05-01 08:22:04 Slp: Parameter 3 : System.ComponentModel.Win32Exception@-2147467259 

(01) 2017-05-01 08:22:04 Slp: Parameter 4 : System.ComponentModel.Win32Exception@-2147467259 

(01) 2017-05-01 08:22:04 Slp: Parameter 5 : SqlEngineConfigAction_install_startup 

(01) 2017-05-01 08:22:04 Slp: Parameter 6 : INSTALL@STARTUP@SQL_ENGINE_CORE_INST 

Explanation

  1. Unable to start the SQLWriter service

 

Trouble Shooting

Services

Explanation

  1. The SQL Server VSS Writer is disabled

 

Microsoft Connect

    • Connect Item :- 3133317
    • Link :- Link
    • Date :- 2017-May-1st
    • Status :- Active
    • Type :- Suggestion

Summary

From an earlier troubleshooting session, we had disabled the SQL Server VSS Writer service.

The Install still went well.  And, the only problem is that the installer was unable to start the disabled service.

 

SQL Server – Upgrading Edition

Background

Needing to upgrade SQL Server from Standard to Enterprise.

 

Script

Though this is do-able through GUI, I prefer to use script and do so from the command line.

Outline

  1. Options
    • /q
      • Specifies that Setup runs in a quiet mode without any user interface.
      • This is used for unattended installations.
    •  /IACCEPTSQLSERVERLICENSETERMS
      • Required to acknowledge acceptance of the license terms
    • /ACTION
      • Required to indicate the installation workflow. Supported values:
        • editionupgrade
    • /INSTANCENAME
      • Instance Name
        • For Default Instance, please specify MSSQLSERVER
    • /PID
      • Product Key
        • Please specify the Product Key

Sample Script

Here is a sample script:


REM Setup.exe /q /ACTION=editionupgrade /INSTANCENAME=<MSSQLSERVER or instancename> /PID=<PID key for new edition>" /IACCEPTSQLSERVERLICENSETERMS

REM Set Instance Name
set _instance=MSSQLSERVER

REM Specifies the product key for the edition of SQL Server
set _ProductKey=

REM Set Location of Install Media
rem set _setupLocation=F:
set _setupLocation=C:\Downloads\Microsoft\SQLServer\v2014\RTM\SQL2014Ent\Extract

"%_setupLocation%\Setup.exe" /q /IACCEPTSQLSERVERLICENSETERMS /ACTION=editionupgrade /INSTANCENAME=%_instance% /PID=%_ProductKey% 

 

Note

  1. Please edit and ensure that ProductKey is entered in _ProductKey

 

GUI

If you are a GUI person, here are your screen shots.

  1. Run setup.exe
    • Screens
      • Window – SQL Server Installation Center
        • On the “SQL Server Installation Center” window, access the “Maintenance” Tab
        • In the Maintenance Tab, select the “Edition Upgrade” button
      • Window – Upgrade the Edition for SQL Server 2014
        • On the “Product Key” window
          • Enter or validate the Product Key
        • On the “License Terms” window
          • Accept the Licensing terms, by clicking on the check-box
        • On the “Global Rules” window
          • The setup application iterates through pre-requisite Checklist
        • On the “Edition Upgrade Rules” window
          • The setup binary goes through check that are pertinent for that edition
            • Is Computer a Domain Controller?
            • Is Service Disabled
            • Is machine/SQL Instance configured for AWE
            • Is Service Account enabled for Lock Pages in memory ( LPIM)
        • On the “Select Instance” window
          • Please choose the SQL Instance to upgrade
        • On the “Feature Rules” window
        • On the “Ready to Upgrade” window
          • Review your choices
          • Make a note of configurationFile.ini
          • Click the upgrade button
        • On the “Complete” window
          • Review the results of the upgrade

Images

Maintenance

Upgrade the Edition for SQL Server 2014 – Product Key

Upgrade the Edition for SQL Server 2014 – License Terms

Upgrade the Edition for SQL Server 2014 – Global Rules

 

Upgrade the Edition for SQL Server 2014 – Edition Upgrade Rules

Upgrade the Edition for SQL Server 2014 – Select Instance

 

Upgrade the Edition for SQL Server 2014 – Feature Rules

Upgrade the Edition for SQL Server 2014 – Ready to upgrade edition

 

References

  1. Developer Network
    • SQL Server 2016 Technical Documentation SQL Server Installation  Install SQL Server 2016
      Link

SQL Server Life Cycle Support

 

Intro

My Director has been behind for a while here.

The imperatives are:

  1. Prepare Inventory list of all SQL Server Installs; the server name and current Version Number
  2. Apply latest Service Packs to all SQL Server Instances that are out of compliance
  3. Chart Upgrade path for the next few years to ensure that we narrow the list of versions that we are supporting

 

SQL Server Life Cycle Support

Stated below are the “Release to Manufacturing” (RTM) and Last Service Pack dates for the various versions of SQL Server.

We also noted the End of Mainstream and End of Extended Support where one has been officially announced by Microsoft.

 

Version Service Pack Release Date End of Mainstream End of Extended
SQL 2016 SP1 RTM :-  2016-June-1st
SP1   :-   2016-Nov-16th
 SQL 2014  SP2 RTM :- 2014-April-1st
SP2   :- 2016-July-11th
 SQL 2012  Sp3 RTM :- 2012-Mar-6th
SP3 :- 2015-Nov-23rd
 SQL 2008/R2  SP3 RTM :- 2010-April-21st
SP3 :- 2014-Sept-26th
 July 8th, 2014  July 9th, 2019
 SQL 2008  SP4 RTM :- 2008-April-7th
SP4 :- 2014-Sept-30th
 Jan 14th, 2014  Jan 8th, 2019
 SQL 2005  Sp4 RTM :- 2005-Nov-7th
SP4 :- 2010-Dec-17th
 April 12th, 2011  April 12th, 2016
 SQL 2000  SP4 RTM :- 2000-Nov
SP4 :- 2005-May-6th
 April 2008  April 9th, 2013

 

 

Suggestion

  1. v2005, v2000
    • Upgrade all current installs to 2014 and v2016
  2. v2008 & v2008/R2
    • Identify instances running v2008 and v2008/R2
    • Consult with clients and corresponding vendors
    • Plan and target upgrade for 2nd and 3rd quarter 2017 and First half of 2018

Current Landscape

  1. We do not have any SQL Instances running v2000, v2005, v2008
  2. We have 5 instances running v2008-R2

 

References

Microsoft – SQL Server Release Services

  1. 2008 and 2008-R2
    • End of Mainstream support for SQL Server 2008 and SQL Server 2008 R2
      Link
  2. 2000
    • End of Extended Lifecycle Support for SQL Server 2000 Service Pack 4
      Link

 

Products & Service Pack

SQL Server 2014

  1. SQL Server 2014 – RTM
    Link
  2. Server & Tools Blogs > Data Platform Blogs > SQL Server Release Services
    SQL Server 2014 Service Pack 2 is now Available !!!
    Link

 

Toad World – Release Date Calendar

  1. SQL Server 2008 Release Date Calendar
    Link
  2. SQL Server 2005 Release Date Calendar
    Link
  3. SQL Server 2000 Release Date Calendar
    Link

Microsoft Build Versions

  1. All
    1. SQL Server and Updates Builds Numbers
      Link
  2.  v2016
    • SQL Server 2016 build versions
      Link
  3. v2014

Service Pack List

  1. Microsoft SQL Server Version List
    https://sqlserverbuilds.blogspot.com/