End of Mainstream support for SQL Server 2008 and SQL Server 2008 R2
We would like to remind all customers that Mainstream Support for SQL Server 2008 and SQL Server 2008 R2 has ended on July 8, 2014. Microsoft is ending support for these products as part of our Support Lifecycle policy, found in https://support.microsoft.com/lifecycle.
Customers are encouraged to prepare and execute on their upgrade and/or sustained engineering plans as early as possible for these SQL versions. Remaining current on your SQL Server version ensures that your product remains supported per the Support Lifecycle policy.
Additionally, your software benefits from the many enhancements, fixes, and security updates provided through the latest releases.
For both SQL Server 2008 and SQL Server 2008 R2, Microsoft will continue to provide technical support which also includes security updates during the duration of extended support. See the table below for extended support end date. Non-security hotfixes for these versions will be offered only to customers who have an Extended Hotfix Support agreement. Please refer to Extended Hotfix Support – Microsoft for more information.
Products Released |
Lifecycle Start Date |
Mainstream Support End Date |
Extended Support End Date |
Service Pack Support End Date |
SQL Server 2008 |
11/6/2008 |
7/8/2014 |
7/9/2019 |
4/13/2010 |
SQL Server 2008 Service Pack 1 |
3/31/2009 |
Not Applicable |
Not Applicable |
10/11/2011 |
SQL Server 2008 Service Pack 2 |
9/24/2010 |
Not Applicable |
Not Applicable |
10/9/2012 |
SQL Server 2008 Service Pack 3 |
10/6/2011 |
Review Note |
Review Note |
|
SQL Server 2008 R2 |
7/20/2010 |
7/8/2014 |
7/9/2019 |
7/10/2012 |
SQL Server 2008 R2 Service Pack 1 |
7/12/2011 |
Not Applicable |
Not Applicable |
10/8/2013 |
SQL Server 2008 R2 Service Pack 2 |
7/26/2012 |
Review Note |
Review Note |
|
Resources:
Comments
Anonymous
July 09, 2014
and the announced Service Packs for these two version, mean what for main stream support?Anonymous
July 09, 2014
Hello, This is nice blog. If you have some issues with microsift then You can find solution on http://pcstartech.us/Anonymous
July 10, 2014
If you follow your CU schedule 2008 SP4 could be out this month and 2008R2 SP3 next month. Can we get an indication of when these service packs will actually appear please? Thanks ChrisAnonymous
September 07, 2014
We are using sql2008 r2 database and after the shrink database, .ldf file (Log file) size not reduce. Can anyone help?Anonymous
October 01, 2014
can the table be updated to include the latest releases of SP3 and SP4 for SQL 2008 and 2008 R2 respectively?Anonymous
February 25, 2015
Might be paid service tagged under extended supportAnonymous
March 05, 2015
PFA for updated information also please correct me if any wrong information is there in the blog venkatsangusqldba.blogspot.in/.../information-for-sql-server-end-of.htmlAnonymous
August 24, 2015
I have a problem on MS SQL2008r2: Error: ApplicationExperienceInfrastructure" warning when you try to install the Directory Sync tool in Windows Server 2012Anonymous
October 27, 2015
Hi folks, What can i infer from this article, can i or not buy SQL 2008 Enterprise licenses? Thank you! ShuhratAnonymous
November 11, 2015
Shuhrat Dont buy sql 2008 any more instead buy sql2014Anonymous
October 07, 2016
Hello,Please can I confirm the EOL for SQL Server 2008 R2 SP3.Your blog states 2019, yet the Microsoft Lifecycle page states 2015.Kind Regards,Mike- Anonymous
October 21, 2016
The support lifecycle that you are referring to is the RTM version. Once we release a Service Pack, the minimum supported version changes. The EOL for the latest Service Packs for SQL Server 2008 and 2008 R2 is listed below:SQL Server 2008 R2 SP3: https://support.microsoft.com/en-gb/lifecycle/search?alpha=SQL%20server%202008%20Service%20Pack%204SQL Server 2008 SP4: https://support.microsoft.com/en-gb/lifecycle/search?alpha=Microsoft%20SQL%20Server%202008%20Service%20Pack%204
- Anonymous
Anonymous
October 10, 2016
This is not reflected on the Microsoft product lifecycle pages.https://support.microsoft.com/en-gb/lifecycle/search?alpha=SQL%20server%202008can these please be updated to reflect the dates shown below- Anonymous
October 21, 2016
The support lifecycle is based on the latest Service Pack. This is documented at:SQL Server 2008 R2 SP3: https://support.microsoft.com/en-gb/lifecycle/search?alpha=SQL%20server%202008%20Service%20Pack%204SQL Server 2008 SP4: https://support.microsoft.com/en-gb/lifecycle/search?alpha=Microsoft%20SQL%20Server%202008%20Service%20Pack%204
- Anonymous
Anonymous
October 18, 2016
Does not have SP3 listed for R2- Anonymous
October 21, 2016
Thanks for pointing it out. Applies to SP3 for SQL Server 2008 R2 as well. See https://support.microsoft.com/en-us/lifecycle/search?alpha=Microsoft%20SQL%20Server%202008%20R2%20Service%20Pack%203- Anonymous
November 17, 2016
Are these dates valid for the Express versions of 2008 R2?- Anonymous
November 18, 2016
These dates are the same for any Edition under the SQL Server 2008 and 2008R2 code branch.
- Anonymous
- Anonymous
January 30, 2017
We have a system that can only run on Windows Server 2008 R2 SP2, can you please confirm the lifespan of support? We have it as 2020 but I would like some official clarification.Thanks in advance.- Anonymous
January 31, 2017
Please check the lifecycle support policy for Windows Server. This has the most updated support policy dates: https://support.microsoft.com/en-us/lifecycle/search?alpha=Windows%20Server%202008%20R2
- Anonymous
- Anonymous
- Anonymous
Anonymous
December 02, 2016
I have a sting '101|1|1|2|3|4|5|6|7|8|9|10##102|1|1|2|3|4|5|6|7|8|9|10' want to split in row column values like split with '##' for rows and | for columnsOutputid val1 val2 val3 val4 val5 val6 val7 val8 val9 val10101 1 2 3 4 5 6 7 8 9 10102 1 2 3 4 5 6 7 8 9 10- Anonymous
December 28, 2016
SQL Server 2016 has a STRING_SPLIT T-SQL function: https://msdn.microsoft.com/en-us/library/mt684588.aspx. We recommend posting such questions on StackOverflow for faster response and also having the community help you with such issues. You will need to use this function and T-SQL or other custom code to get this done.
- Anonymous