Select the product you need help with
FIX: Access violation when you put a FILESTREAM-enabled database offline in SQL Server 2008 R2 or in SQL Server 2012Article ID: 2800013 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 2 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 2 fix release. On This PageSymptomsAssume that you try to set the state of a FILESTREAM-enabled database in Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 to "OFFLINE." In this situation, an access violation may occur, and you may receive the following error message: Msg 5069, Level 16, State 1, Line 1 ALTER DATABASE statement failed. ResolutionCumulative update informationCumulative Update 7 for SQL Server 2012The 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 2012, click the following article number to view the article in the Microsoft Knowledge Base:2823247 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/2823247/
)
Cumulative update package 7 for SQL Server 20122692828
(http://support.microsoft.com/kb/2692828/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was releasedCumulative Update 3 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2812412 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 SP1 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/2812412/
)
Cumulative update package 3 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 releasedCumulative Update 5 for SQL Server 2008 R2 SP2The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:2797460 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 SP 2 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/2797460/
)
Cumulative update package 5 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 releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. WorkaroundTo work around this issue, restart the SQL server to bring the database online. PropertiesArticle ID: 2800013 - Last Review: April 15, 2013 - Revision: 3.0 Applies to
| Article Translations
 |
Back to the top
