tim laqua dot com » ssrs http://timlaqua.com Thoughts and Code from Tim Laqua Sun, 09 May 2010 15:25:58 +0000 en hourly 1 http://wordpress.org/?v=3.0 Reporting Services (SSRS/MSRS) 2008 Error: Set used with the complement operator must have all members from the same level http://timlaqua.com/2009/10/reporting-services-ssrsmsrs-2008-error-set-used-with-the-complement-operator-must-have-all-members-from-the-same-level/ http://timlaqua.com/2009/10/reporting-services-ssrsmsrs-2008-error-set-used-with-the-complement-operator-must-have-all-members-from-the-same-level/#comments Thu, 01 Oct 2009 19:38:06 +0000 Tim http://timlaqua.com/?p=244 When you use the Not In operator in a SSRS 2008 MDX query filter to exclude a named set, it uses a the complement operator in the constructed MDX. This is fine as long as "all members [are] from the same level." Since you got this error, they are not ;-) You can get around this by using the Except() MDX function instead of letting SSRS use the Complement operator

In the ReportServerService log, you'll see something like this:
Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Query (..., ...) Set used with the complement operator must have all members from the same level.

Original filter
Dimension: Time
Hierarchy: Calendar Date
Operator: Not In
Filter Expression: [Today]

New filter
Dimension: Time
Hierarchy: Calendar Date
Operator: MDX
Filter Expression: Except([Time].[Calendar Date].[Calendar Date].MEMBERS, [Today])

]]> http://timlaqua.com/2009/10/reporting-services-ssrsmsrs-2008-error-set-used-with-the-complement-operator-must-have-all-members-from-the-same-level/feed/ 0 Searching for keywords in all Reporting Services (SSRS) reports http://timlaqua.com/2008/09/searching-for-keywords-in-all-reporting-services-ssrs-reports/ http://timlaqua.com/2008/09/searching-for-keywords-in-all-reporting-services-ssrs-reports/#comments Thu, 11 Sep 2008 16:03:24 +0000 Tim http://timlaqua.com/?p=38 During impact analysis for any changes to existing database tables, cube dimensions, cube measures, etc, it's nice to know which reports are going to horribly break before your end-users let you know about it ;-) All of the rdl content for reports uploaded to SSRS is stored in the ReportingServices database in the Content column of the Catalog table (in binary, of course) so here's what I came up with to get the list of soon to be broken reports:

SELECT [Path], ContentText
FROM
(
SELECT [Path], cast(cast([content]AS varbinary(8000)) AS varchar(8000)) AS [ContentText]
FROM [catalog] cat WITH(nolock)
WHERE [type]=2
) a
WHERE ContentText LIKE '%ColumnName%' 
	OR ContentText LIKE '%columnname%' 
	OR ContentText LIKE '%MeasureName%' 
	OR ContentText LIKE '%AttributeName%' 
	OR ContentText LIKE '%etc...%'
]]> http://timlaqua.com/2008/09/searching-for-keywords-in-all-reporting-services-ssrs-reports/feed/ 0