FIX: Error message when you try to create a currency conversion against an Oracle data source in SQL Server 2005 Analysis Services: "The following statement executed when creating named query: SELECT 'Reporting Currency'"

Consider the following scenario. You create a Microsoft SQL Server 2005 Analysis Services project in the Business Intelligence Development Studio. You create a data source that connects to an Oracle database by using the OracleClient data provider. Then, you try to create a currency conversion by using the Business Intelligence Wizard against the Oracle data source. In this scenario, you receive the following error message:

This problem occurs because the conversion script that the Business Intelligence Wizard generates is incompatible with the OracleClient data provider.

Cumulative update information

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 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: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 2005 fix release. Microsoft recommends 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:Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2005 Service Pack 2 installed to apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Files that are updated for SQL Server 2005 Analysis Services

Files that are updated for SQL Server 2005 tools

To work around this problem, follow these steps:

1. In an instance of SQL Server 2005, create a database that has the same schema as an Oracle database.
2. Create a working copy of the Analysis Services project, and then open the working copy in the Business Intelligence Development Studio.
3. In the working copy, update the data source to connect to the SQL Server 2005 database that you created in step 1.
4. In the working copy, create a currency conversion by using the Business Intelligence Wizard against the Oracle data source.
5. On the Define Currency Conversion page of the Business Intelligence Wizard, save the conversion script under New currency conversion script, and then click Finish.
6. In the working copy, right-click the Report Currency named query in the same data source view as the original Analysis Services project, and then click Edit Named Query.
7. In the Edit Named Query dialog box, save the SQL expression that constructs the Report Currency named query.
8. In the original Analysis Services project, create the Reporting Currency named query by using the same SQL expression that you saved in step 7.
9. In the original Analysis Services project, run the conversion script that you saved in step 5.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Critical information for SQL Server 2005 Analysis Services

A known issue in Cumulative Update 7 for SQL Server 2005 Analysis Services

Consider the following scenario. You install Cumulative Update 7 for SQL Server 2005 Service Pack 2 (SP2). In SQL Server Profiler, you start or stop a trace. You run a query whose execution time exceeds the value in the ForceCommitTimeout server setting. In this scenario, all the running queries on the server are cancelled.

To work around this issue, do not execute MDX queries before you start or stop a trace. For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 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:For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: 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:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.