Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article lists the bugs that are fixed in the Community Technology Preview (CTP) version of Microsoft SQL Server 2012 Service Pack 1 (SP1).


  • This is a CTP version of SQL Server 2012 SP1. This version is not supported by Microsoft Customer Support Services. You can submit your feedback at the following Microsoft Connect website:

    Microsoft SQL Server Connect

  • Other fixes that are not documented may be included in the service pack.

  • This list will be updated when more articles are released.

For more information about how to obtain SQL Server 2012 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

2755533 How to obtain the latest service pack for SQL Server 2012

More Information

In addition to the fixes that are listed in this article, SQL Server 2012 SP1 CTP contains the hotfixes that were included in cumulative update packages that are available for SQL Server 2012.
For more information about the cumulative update packages that are available for SQL Server 2012, 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

The issues that are fixed in this CTP version of the service pack

For more information about the bugs that are fixed in SQL Server 2012 SP1 CTP, click the following article numbers to view the articles in the Microsoft Knowledge Base.

VSTS bug number

KB article number





FIX: Availability group failover takes a long time if a database in the availability group contains a FileTable in SQL Server 2012




FIX: New Availability Group Wizard-generated scripts skip the steps for joining a secondary database to an availability group in SQL Server 2012




FIX: You experience a deadlock condition when you run multiple SSIS packages in SQL Server 2012




FIX: SQL Server Data Quality Client stops responding when you try to delete a data quality project after you install Cumulative Update 1 for SQL Server 2012




SQL Server 2012 DQS Export to 64-bit .xls Excel file fails with error


Resolutions to the following issues are also included in SQL Server 2012 SP1 CTP.

VSTS bug number



"View Sample Records" is disabled in the "discovery" process in SQL Server Data Quality Services (DQS).


Vertical scroll of Log Severity data grid is missing in DQS.


New clause is incorrectly added to previous rule of current or previous domain in DQS.


Empty "Name" column is not published as NULLin DQS.


A child domain of Composite Domain is not formatted when the child domain has a specific formatting.


A read-only user who is in a group that has update permission can perform an update operation.


"IsolatedStorageException" exception when you try to access an entity in Master Data Services in InPrivate Browsing mode in Internet Explorer.


A date time column does not increase for every 20 rows that are updated to the Remote Date Services in SQL Server 2012.


No results are displayed when you search a value in a Hebrew string.


An unhandled exception occurs when you try to sign in to a Data Quality Project in DQS.


"File download failed, check that the export destination file does not already exist." error when you try to export to an Excel file in DQS.


"The given key was not present in the dictionary" error message when you approve the changes in a newly-added term-based relation in DQS.


Explicit hierarchies are corrupted because of circular references in SQL Server 2012.


"Windows PowerShell is not installed on this server" error when you launch Configuration Manager.


Installation operation fails when you run the DQSInstaller.exe file to install DQS server if you specify the "&" character in the password for the database master key.


"Failed to save Configuration Name" error when a Windows user whose name has accented characters tries to open a data quality project by using Data Quality Client.


Updated knowledge bases cannot be used in an already-open Cleansing Project in DQS.


Incorrect error message is displayeds when you try to use Data Quality Client.

Note In this description, the word "displayeds" is a misspelling for the word "displayed."


The sort order is corrupted when you run the [mdm].[udpAttributeSave] stored procedure against an existing attribute in SQL Server 2012.


"Login failed for user '<Domain>\<User>'. Failed to open the explicitly specified database 'DQS_MAIN'. [CLIENT: <local machine>]" error in Master Data Services if DQS is not installed.


Cannot publish business rules when attributes contain "&" in the attribute name in Master Data Services.


An access violation occurs when executing a substring function together with an invalid offset by using remote procedure call (RPC).


"Date Postfix Argument Expected" error if you create a "has changed" business rule for an attribute of "DateTime" type in Master Data Services web UI.


"An unexpected error occurred during the last correction process" error when you try to run DQS data cleansing in SQL Server 2012.


DQS violation error message is hard to understand when you use Master Data Services web UI or Excel Add-in.


Cannot hard delete any soft-deleted members from the Master Data Services database.


Incorrect popup message when you create matching policy and then run a data matching project in DQS.


The .NET Framework 4.5-based application stops responding instead of handling the exception when you use the Master Data Services Add-in for Excel.


"String or binary data would be truncated" error when the length of a SQL Server Integration Services (SSIS) DQS cleansing component name is longer than 32 characters.


"SQL46010: Incorrect syntax near SPARSE" error in a SQL Server Data Tools (SSDT) project.


The TSqlParser.ParseSubQueryExpressionWithOptionalCTE() method returns NULL for a SELECTstatement that contains a common table expression (CTE) and a pair of parentheses in an SSDT project.


You cannot publish a business rule when the rule contains a "Equals a Concatenated Value" or "Must be Unique" action, and the selected attribute name has more than 128 characters.


For more information about how to determine the current SQL Server version and edition, click the following article number to view the article in the Microsoft Knowledge Base:

321185 How to determine the version and edition of SQL Server and its components

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!