Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: Access violation when you run a DAX or MDX query against a tabular model database through a BI semantic model connection in SQL Server 2012
Article ID: 2693652 - View products that this article applies to.
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 create a BI semantic model connection that redirects to an analysis services tabular model database in Microsoft SQL Server 2012. Then, a DAX or MDX query is sent to the tabular model database. In this situation, an access violation might occur if the following conditions are true:
Cumulative update information
SQL Server 2012The 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:
2703275Note 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/2703275/LN/ )Cumulative update package 2 for SQL Server 2012
2692828Microsoft 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.
(http://support.microsoft.com/kb/2692828/LN/ )The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2693652 - Last Review: June 19, 2012 - Revision: 2.0