DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2406666 - Last Review: November 20, 2012 - Revision: 6.0

Microsoft distributes Microsoft SQL Server 2008 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 fix release.

On This Page

Symptoms

Consider the following scenario:
  • You use Microsoft Business Intelligence Development Studio (BIDS) to connect to a Microsoft SQL Server 2008 Analysis Services (SSAS) database, a Microsoft SQL Server 2012 Analysis Services (SSAS 2012) database, or a Microsoft SQL Server 2008 R2 Analysis Services (SSAS 2008 R2) database.
  • You click the Aggregations tab for a cube that uses a Teradata data source in the cube designer.
  • You use the Aggregation Design Wizard to design aggregations for a partition of a back-end Teradata table in the cube.
  • The length of the schema name for the Teradata table plus the length of the table name is at least 30 bytes.
  • In the Aggregation Design Wizard window, you click Count on the Specify Object Counts page.
In this scenario, you receive the following error message:
[Teradata Database] [3737] Name requires more than 30 bytes in LATIN internal form.

Cause

This issue occurs because the length of the auto-generated table alias for the count operation exceeds the 30-byte limit. When this limit is exceeded, the count operation cannot run.

Resolution

Cumulative update information

Cumulative update package 1 for SQL Server 2012 Service Pack 1

The 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  (http://support.microsoft.com/kb/2765331/ ) Cumulative update package 1 for SQL Server 2012 Service Pack 1
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:
2772858  (http://support.microsoft.com/kb/2772858/ ) The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

SQL Server 2008 R2 Service Pack 2

The 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 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2754552  (http://support.microsoft.com/kb/2754552/ ) Cumulative update package 3 for SQL Server 2008 R2 Service Pack 2
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 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  (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 2012

The fix for this issue was first released in Cumulative Update 4. 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:
2758687  (http://support.microsoft.com/kb/2758687/ ) Cumulative update package 4 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  (http://support.microsoft.com/kb/2692828/ ) The SQL Server 2012 builds that were released after SQL Server 2012 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 9. 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:
2756574  (http://support.microsoft.com/kb/2756574/ ) Cumulative update package 9 for SQL Server 2008 R2 Service Pack 1
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:
2567616  (http://support.microsoft.com/kb/2567616/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 7 for SQL Server 2008 Service Pack 3. 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:
2738350  (http://support.microsoft.com/kb/2738350/ ) Cumulative Update package 7 for SQL Server 2008 Service Pack 3
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 Service Pack 3 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:
2629969  (http://support.microsoft.com/kb/2629969/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2715951  (http://support.microsoft.com/kb/2715951/ ) Cumulative update package 11 for SQL Server 2008 Service Pack 2
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 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:
2402659  (http://support.microsoft.com/kb/2402659/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
After apply this hotfix, the auto-generated table alias is truncated if it exceeds the 30-byte limit.

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 about how to specify object counts in the Aggregation Design Wizard, go to the following MSDN website:
How to specify object counts (http://msdn.microsoft.com/en-us/library/ms178928(v=SQL.100).aspx)
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897  (http://support.microsoft.com/kb/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  (http://support.microsoft.com/kb/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  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

Applies to
  • Microsoft SQL Server 2008 Service Pack 2, when used with:
    • Microsoft SQL Server 2008 Analysis Services
  • Microsoft SQL Server 2008 R2 Service Pack 2
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
  • Microsoft SQL Server 2012 Express
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2406666
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support