Microsoft distributes Microsoft SQL Server 2012 Service Pack 1 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 2012 Service Pack 1 fix release.
Introduction
This article describes several new features that are added in the cumulative updates for Microsoft SQL Server 2012 and Microsoft SQL Server 2008 R2.
More Information
Features that are added in this cumulative update
Feature 1: Backup and restore from SQL Server to Microsoft Azure Blob storage
Expanding on current backup storage options, native SQL Server backups can now be stored in Microsoft Azure Blob storage. In this release, backups to Microsoft Azure Blob storage are supported by using Transact-SQL and Server Management Objects (SMO). This improvement can be used to back up a SQL Server database on an on-premises instance or on an instance of SQL Server that is running in a hosted environment, such as the Microsoft Azure Virtual Machine. For more details, see SQL Server Backup and Restore with Microsoft Azure Blob Storage Service.Feature 2: Expanding the supported features of SQL Server Sysprep to include Analysis Services, Integration Services, and most shared featuresEarlier versions of SQL Server supported the preparing of images by using SQL Server Sysprep. This enabled images to be prepared with desired features and then completed later. However, there were many major features that were not supported by SQL Server Sysprep. Expanding the supported features for SQL Server Sysprep to include SQL Server Analysis Services, SQL Server Integration Services, and shared features enables SQL Server Sysprep to be used in a wider variety of image preparation scenarios.
How to use the new features
Feature 1: Backup and restore from SQL Server to Microsoft Azure Blob storageTo write a backup to Microsoft Azure Blob storage, you must first create a Microsoft Azure Storage account, then create a SQL Server credential to store storage account authentication information. You can use Transact-SQL or SMO to issue backup and restore commands.The following Transact-SQL examples illustrate creating a credential, performing a full database backup, and restoring the database from the full database backup. For a complete walkthrough of creating a storage account and performing a simple restore, see Tutorial: Getting Started with SQL Server Backup and Restore to Microsoft Azure Blob Storage Service. You can also see Backup and Restore Best Practices (Microsoft Azure Blob Storage Service).Creating a credentialThe following example creates a credential that stores the Microsoft Azure Storage authentication information:
IF NOT EXISTS( SELECT * FROM sys.credentialsWHERE credential_indentity = 'mycredential')CREATE CREDENTIAL mycredential WITH IDENTITY = 'mystorageaccount',SECRET = '<storage access key>';
Backing up a complete databaseThe following example backs up the AdventureWorks2012 database to the Microsoft Azure Blob storage service:
BACKUP DATABASE AdventureWorks2012TO URL = 'https://mystorageaccount.blob.core.windows.net/mycontainer/AdventureWorks2012.bak' WITH CREDENTIAL = 'mycredential',STATS = 5;GO
Restoring a databaseThe following example restores a full database backup:
RESTORE DATABASE AdventureWorks2012 FROM URL ='https://mystorageaccount.blob.core.windows.net/mycontainer/AdventureWorks2012.bak'WITH CREDENTIAL = 'mycredential',STATS = 5;GO
Feature 2: Expanding the supported features of SQL Server Sysprep to include Analysis Services, Integration Services, and most shared featuresTo use the SQL Server Sysprep functionality that is included in SQL Server 2012 SP1 CU2, follow these steps:
-
Create a slipstream package that includes the SQL Server 2012 SP1 CU2 package.
-
Run setup to initiate SQL Server Sysprep preparation.
For more information about how to install SQL Server 2012 by using SysPrep, go to the following MSDN website:
Cumulative update information
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 7 for SQL Server 2012 SP1 /en-us/help/2894115
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Cumulative update 8 for SQL Server 2012The fix for this issue was first released in Cumulative Update 8. 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:
2844205 Cumulative update package 8 for SQL Server 2012Note 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Cumulative Update 7 for SQL Server 2008 R2 Service Pack 2 (SP2)The 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 2, click the following article number to view the article in the Microsoft Knowledge Base:
2844090 Cumulative update package 7 for SQL Server 2008 R2 Service Pack 2Note 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 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:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
