Select the product you need help with
FIX: An incorrect value is stored in the TIME_ZONE column of the BACKUPSET table in SQL Server 2008 R2 or in SQL Server 2012Article ID: 2697983 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) fix release. On This PageSymptomsIn Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012, the daylight saving time (DST) for the United States begins at 02:00 on March 2 and ends at 02:00 on November 1. However, beginning in 2007, the DST for the United States was changed to the following:
ResolutionCumulative update informationCumulative update package 1 for SQL Server 2012 Service Pack 1The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2765331 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2765331/
)
Cumulative update package 1 for SQL Server 2012 Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was releasedSQL Server 2012The fix for this issue was first released in Cumulative Update 3 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2723749 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2723749/LN/
)
Cumulative update package 3 for SQL Server 20122692828 You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.
(http://support.microsoft.com/kb/2692828/LN/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released SQL Server 2008 R2 Service Pack 2The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2720425 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2720425/
)
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released SQL Server 2008 R2 SP1The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2703282 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2703282/
)
Cumulative update package 7 for SQL Server 2008 R2 SP12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was releasedMore informationThe incorrect value for the time zone offset is only stored in the BACKUPSET table for backups that have been created between 02:00 on March 2 and 02:00 on November 1. This preventative hotfix does not change an existing incorrect value for the time zone offset in the BACKUPSET table. After you apply the hotfix, any new backups that have been created between 02:00 on March 2 and 02:00 on November 1 will have the correct value for the time zone offset. StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2697983 - Last Review: November 20, 2012 - Revision: 5.0 Applies to
| Article Translations |
Back to the top
