Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Services / Notification Services / April 2009

Tip: Looking for answers? Try searching our database.

Bug: "Dynamic MDX Queries" don't work as described

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mark Landry - 27 Mar 2009 00:36 GMT
In short, "Dynamic MDX Queries" don’t work as described in the BOL.
I’ve lifted the sample code directly, tried to run it, and it fails.
It’s documented at http://msdn.microsoft.com/en-us/library/ms172589(SQL.90).aspx

The “Analysis Services Event Provider” queries a SQL table, generates
XML output, passes it through an XSLT style sheet, and generates an
MDX query dynamically. Using the documented example, no MDX is created
as seen in the event log error below: (The “MDX Query String” is
blank).

Event Type:       Error
Event Source:    NotificationServices
Event Category: None
Event ID:           2976
Date:                3/26/2009
Time:                6:59:10 PM
User:                N/A
Computer:         MyServer
Description:
Description: The AnalysisServicesProvider event provider failed while
running an MDX query. The provider will be terminated.
EventParameters:
 Provider Name: TerminalEventNsEventProvider
 MDX Query String:

Description: ExecuteReader: CommandText property has not been
initialized
InstanceName: IodNS
ApplicationName: DashboardNotifications
Component: Event collection
Thread: 10

I’ve tried countless variations and “pass-through” XSLT and I can’t
get anything past this point.

Can someone at MS redirect to the SSNS support group?
Mark Landry - 06 Apr 2009 15:37 GMT
We discovered two related bugs in the ‘Analysis Services Event
Provider’ component of Notification Services 2005.

Bug #1 The documentation describes the following XML :

<rows>
   <row Employee="Ken J Snchez" />
   <row Employee="Laura F Norman" />
   <row Employee="Terry Lee Duffy" />
   <row Employee="Gordon L Hee" />
</rows>
<slicers>
   <slicer Calendar Time="2002"/>
</slicers>

This is non-standard XML as it doesn’t have a root node. Therefore,
XSLT translations using this code will always fail producing an empty
MDX query.

Bug#2: If the SlicerQuery argument is present (as shown below), even
if it’s value is empty, the Event Provider will add an empty
<slicers></slicers> tag to the xml rendering the result unparse-able
as described above.

<HostedProvider>
   <ProviderName>DynamicASEventProvider</ProviderName>
...
       <Argument>
           <Name>SlicerQuery</Name>
           <Value></Value>
       </Argument>
...
   </Arguments>
</HostedProvider>
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.