Microsoft distributes Microsoft SQL Server 2012 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 fix release.
Assume that you use a user name that contains an accented character or a special character to log on to Windows. Then, you try to open or create a knowledge base in the Data Quality Client in SQL Server 2012. In this situation, the operation fails. Additionally, you receive the following error message:
Failed to save Configuration Name: RecentList:KB:domain\username
This issue occurs because the "Name" column uses the Varchar(255) data type in the DQS_MAIN.dbo.A_CONFIGURATION table. This data type cannot be used to store Unicode characters. This includes accented characters.
Note After you apply this hotfix, the Name column uses the NVarchar data type instead. This data type supports Unicode characters and accented characters.
Cumulative update information
SQL Server 2012
The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012 Service Pack RTM. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703275 Cumulative update package 2 for SQL Server 2012
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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft SQL Server 2012 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2012 Service Pack RTM hotfix to an installation of SQL Server 2012 Service Pack RTM. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
After you apply this cumulative update, the schema of the DQS catalogs is not updated and the SQL CLR assemblies keep the DQS catalogs. You must run the DQSInstaller.exe –upgrade command to update the DQS catalogs. For more information, visit the following Microsoft website:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around the issue, use another user account that does not have Unicode characters in the user name. If you do not want to log off the current user account, follow these steps to run the Data Quality Client:
Click Start, click All Programs, click Microsoft SQL Server 2012, click Data Quality Services, then hold Shift and right-click Data Quality Client.
Click Run as a different user.
Enter the other username and password, and then click OK.
Note The alternative user account must meet the following requirements:
The user account is a valid Windows login in the SQL Server database engine instance.
The user account is a member of the dqs_administrator role, the dqs_kb_editor role, or the dqs_kb_operator role in the DQS_MAIN database of the SQL Server database engine instance.
The user account has appropriate read and write access to the source or destination tables in the SQL Server database engine or the Excel workbooks in the file system that is used for Data Quality Services (DQS).