Hi,
I saw some threads about using parent-child dimensions in a reporting
services report on an OLAP cube in this newsgroup. I have the same problem
that I didn't get the nesting, I want, because reporting services didn't
render it. I tried with the UniqueName and ParentUniqueName properties, but
I only get a hierarchy of Level2 and no deeper. Does anyone knows a solution
in the meantime?
Thanks
HansI have managed to get round this problem by creating a virtual
dimension of level 3 and then doing a cross join on the 2 dimensions.
This will get you your nesting
Showing posts with label olap. Show all posts
Showing posts with label olap. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
partitioning a table question...
Hi,
I have to plan a datawarehouse structure where the primary reporting usage
is to list detailed information about customers.
And also, we have OLAP cube for analysis purpose.
I'll have 100 000 customers and a fact table containing between 35 to
45millions of rows by year. (we also have 2 other fact table with 5 to
6millions of rows by year)
Generally, this fact table is filtered for a particular organizational unit
and for data in 1 year. (for report generation using report server)
So, I plan to partition my fact table by organizational unit and by year.
But I have 180 units.
Does the partitioning will works fine with 180 * 5 years = 900 tables?
on this article:
http://msdn.microsoft.com/library/d...ndw.
htm
there is a note that the maximum number of tables is 256.
But the performance gain can be very high!
The estimated size of the DW is 10gb / year (maybe more with additional
indexes)
My DTS package is ready to support partioning table loading. (the package
automatically create the new table, indexes and update the view for each
detected partition in the staging source table)
My users access my reportserver interactively, scheduling anything is not an
option.
For higher analysis, my olap cubes are ready.
thanks for your feedback.
Jerome.Hi Jerome:
I have some kind of "rule". Just make a partition for each 1 GB of data.
Or doing it for a year, would be great. If you need more granularity, give
it a try to month partitioning.
Tell me if you need some help on this
Sincerely
Alejandro Leguizamo
MVP SQL Server
Colombia
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:uwuxtzxzEHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have to plan a datawarehouse structure where the primary reporting usage
> is to list detailed information about customers.
> And also, we have OLAP cube for analysis purpose.
> I'll have 100 000 customers and a fact table containing between 35 to
> 45millions of rows by year. (we also have 2 other fact table with 5 to
> 6millions of rows by year)
> Generally, this fact table is filtered for a particular organizational
> unit and for data in 1 year. (for report generation using report server)
> So, I plan to partition my fact table by organizational unit and by year.
> But I have 180 units.
> Does the partitioning will works fine with 180 * 5 years = 900 tables?
> on this article:
> http://msdn.microsoft.com/library/d...nd
w.htm
> there is a note that the maximum number of tables is 256.
> But the performance gain can be very high!
> The estimated size of the DW is 10gb / year (maybe more with additional
> indexes)
> My DTS package is ready to support partioning table loading. (the package
> automatically create the new table, indexes and update the view for each
> detected partition in the staging source table)
> My users access my reportserver interactively, scheduling anything is not
> an option.
> For higher analysis, my olap cubes are ready.
> thanks for your feedback.
> Jerome.
>
>|||but does SQL Server support 500 tables in a partitioned view?
I don't need help about this, I just want to plan correctly.
and I don't want month partition but only year + organizational unit
Because I don't do sum or count aggregation in SQL (or just a little sum
compared of what my cube provide).
Generally my reports contains SQL statement like this:
* Last kown value at a specific date (subquery required) (by customer)
* events which start before and end after a specific date (between
statement) (by customer)
Its the reason of not using monthly partitions, because I never know when
these dates appear in the database.
"Alejo Leguizamo (MVP SQL)" <SQL@.sql.sql> a crit dans le message de news:
%23thX4VC0EHA.1204@.TK2MSFTNGP10.phx.gbl...
> Hi Jerome:
> I have some kind of "rule". Just make a partition for each 1 GB of data.
> Or doing it for a year, would be great. If you need more granularity, give
> it a try to month partitioning.
> Tell me if you need some help on this
> Sincerely
>
> --
> Alejandro Leguizamo
> MVP SQL Server
> Colombia
> "Jj" <willgart@.BBBhotmailAAA.com> wrote in message
> news:uwuxtzxzEHA.3336@.TK2MSFTNGP11.phx.gbl...
>|||Jerome,
Views are based on select statements. A select statement can have a max of
256 tables in the From clause. So the answer to your specific question is
no.
Danny
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:e1ghnJD0EHA.2624@.TK2MSFTNGP11.phx.gbl...
> but does SQL Server support 500 tables in a partitioned view?
> I don't need help about this, I just want to plan correctly.
> and I don't want month partition but only year + organizational unit
> Because I don't do sum or count aggregation in SQL (or just a little sum
> compared of what my cube provide).
> Generally my reports contains SQL statement like this:
> * Last kown value at a specific date (subquery required) (by customer)
> * events which start before and end after a specific date (between
> statement) (by customer)
> Its the reason of not using monthly partitions, because I never know when
> these dates appear in the database.
> "Alejo Leguizamo (MVP SQL)" <SQL@.sql.sql> a crit dans le message de news:
> %23thX4VC0EHA.1204@.TK2MSFTNGP10.phx.gbl...
>|||
sniff
I think I'll do this: partition by organization for the current year and by
year for the history... does this works in a partitioned view?
"Danny" <istdrs@.flash.net> a crit dans le message de news:
7Lkod.23022$Rf1.15232@.newssvr19.news.prodigy.com...
> Jerome,
> Views are based on select statements. A select statement can have a max
> of 256 tables in the From clause. So the answer to your specific question
> is no.
> Danny
> "Jj" <willgart@.BBBhotmailAAA.com> wrote in message
> news:e1ghnJD0EHA.2624@.TK2MSFTNGP11.phx.gbl...
>|||The primary key of the underlying tables in the view must be the same. For
this to work, you will have to query current and history separately with
each haing its own view.
Danny
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:uKoQZzP0EHA.1932@.TK2MSFTNGP09.phx.gbl...
>
> sniff
> I think I'll do this: partition by organization for the current year and
> by year for the history... does this works in a partitioned view?
> "Danny" <istdrs@.flash.net> a crit dans le message de news:
> 7Lkod.23022$Rf1.15232@.newssvr19.news.prodigy.com...
>
I have to plan a datawarehouse structure where the primary reporting usage
is to list detailed information about customers.
And also, we have OLAP cube for analysis purpose.
I'll have 100 000 customers and a fact table containing between 35 to
45millions of rows by year. (we also have 2 other fact table with 5 to
6millions of rows by year)
Generally, this fact table is filtered for a particular organizational unit
and for data in 1 year. (for report generation using report server)
So, I plan to partition my fact table by organizational unit and by year.
But I have 180 units.
Does the partitioning will works fine with 180 * 5 years = 900 tables?
on this article:
http://msdn.microsoft.com/library/d...ndw.
htm
there is a note that the maximum number of tables is 256.
But the performance gain can be very high!
The estimated size of the DW is 10gb / year (maybe more with additional
indexes)
My DTS package is ready to support partioning table loading. (the package
automatically create the new table, indexes and update the view for each
detected partition in the staging source table)
My users access my reportserver interactively, scheduling anything is not an
option.
For higher analysis, my olap cubes are ready.
thanks for your feedback.
Jerome.Hi Jerome:
I have some kind of "rule". Just make a partition for each 1 GB of data.
Or doing it for a year, would be great. If you need more granularity, give
it a try to month partitioning.
Tell me if you need some help on this
Sincerely
Alejandro Leguizamo
MVP SQL Server
Colombia
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:uwuxtzxzEHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have to plan a datawarehouse structure where the primary reporting usage
> is to list detailed information about customers.
> And also, we have OLAP cube for analysis purpose.
> I'll have 100 000 customers and a fact table containing between 35 to
> 45millions of rows by year. (we also have 2 other fact table with 5 to
> 6millions of rows by year)
> Generally, this fact table is filtered for a particular organizational
> unit and for data in 1 year. (for report generation using report server)
> So, I plan to partition my fact table by organizational unit and by year.
> But I have 180 units.
> Does the partitioning will works fine with 180 * 5 years = 900 tables?
> on this article:
> http://msdn.microsoft.com/library/d...nd
w.htm
> there is a note that the maximum number of tables is 256.
> But the performance gain can be very high!
> The estimated size of the DW is 10gb / year (maybe more with additional
> indexes)
> My DTS package is ready to support partioning table loading. (the package
> automatically create the new table, indexes and update the view for each
> detected partition in the staging source table)
> My users access my reportserver interactively, scheduling anything is not
> an option.
> For higher analysis, my olap cubes are ready.
> thanks for your feedback.
> Jerome.
>
>|||but does SQL Server support 500 tables in a partitioned view?
I don't need help about this, I just want to plan correctly.
and I don't want month partition but only year + organizational unit
Because I don't do sum or count aggregation in SQL (or just a little sum
compared of what my cube provide).
Generally my reports contains SQL statement like this:
* Last kown value at a specific date (subquery required) (by customer)
* events which start before and end after a specific date (between
statement) (by customer)
Its the reason of not using monthly partitions, because I never know when
these dates appear in the database.
"Alejo Leguizamo (MVP SQL)" <SQL@.sql.sql> a crit dans le message de news:
%23thX4VC0EHA.1204@.TK2MSFTNGP10.phx.gbl...
> Hi Jerome:
> I have some kind of "rule". Just make a partition for each 1 GB of data.
> Or doing it for a year, would be great. If you need more granularity, give
> it a try to month partitioning.
> Tell me if you need some help on this
> Sincerely
>
> --
> Alejandro Leguizamo
> MVP SQL Server
> Colombia
> "Jj" <willgart@.BBBhotmailAAA.com> wrote in message
> news:uwuxtzxzEHA.3336@.TK2MSFTNGP11.phx.gbl...
>|||Jerome,
Views are based on select statements. A select statement can have a max of
256 tables in the From clause. So the answer to your specific question is
no.
Danny
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:e1ghnJD0EHA.2624@.TK2MSFTNGP11.phx.gbl...
> but does SQL Server support 500 tables in a partitioned view?
> I don't need help about this, I just want to plan correctly.
> and I don't want month partition but only year + organizational unit
> Because I don't do sum or count aggregation in SQL (or just a little sum
> compared of what my cube provide).
> Generally my reports contains SQL statement like this:
> * Last kown value at a specific date (subquery required) (by customer)
> * events which start before and end after a specific date (between
> statement) (by customer)
> Its the reason of not using monthly partitions, because I never know when
> these dates appear in the database.
> "Alejo Leguizamo (MVP SQL)" <SQL@.sql.sql> a crit dans le message de news:
> %23thX4VC0EHA.1204@.TK2MSFTNGP10.phx.gbl...
>|||
sniff
I think I'll do this: partition by organization for the current year and by
year for the history... does this works in a partitioned view?
"Danny" <istdrs@.flash.net> a crit dans le message de news:
7Lkod.23022$Rf1.15232@.newssvr19.news.prodigy.com...
> Jerome,
> Views are based on select statements. A select statement can have a max
> of 256 tables in the From clause. So the answer to your specific question
> is no.
> Danny
> "Jj" <willgart@.BBBhotmailAAA.com> wrote in message
> news:e1ghnJD0EHA.2624@.TK2MSFTNGP11.phx.gbl...
>|||The primary key of the underlying tables in the view must be the same. For
this to work, you will have to query current and history separately with
each haing its own view.
Danny
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:uKoQZzP0EHA.1932@.TK2MSFTNGP09.phx.gbl...
>
> sniff
> I think I'll do this: partition by organization for the current year and
> by year for the history... does this works in a partitioned view?
> "Danny" <istdrs@.flash.net> a crit dans le message de news:
> 7Lkod.23022$Rf1.15232@.newssvr19.news.prodigy.com...
>
partitioning a table question...
Hi,
I have to plan a datawarehouse structure where the primary reporting usage
is to list detailed information about customers.
And also, we have OLAP cube for analysis purpose.
I'll have 100 000 customers and a fact table containing between 35 to
45millions of rows by year. (we also have 2 other fact table with 5 to
6millions of rows by year)
Generally, this fact table is filtered for a particular organizational unit
and for data in 1 year. (for report generation using report server)
So, I plan to partition my fact table by organizational unit and by year.
But I have 180 units.
Does the partitioning will works fine with 180 * 5 years = 900 tables?
on this article:
http://msdn.microsoft.com/library/de...itionsindw.htm
there is a note that the maximum number of tables is 256.
But the performance gain can be very high!
The estimated size of the DW is 10gb / year (maybe more with additional
indexes)
My DTS package is ready to support partioning table loading. (the package
automatically create the new table, indexes and update the view for each
detected partition in the staging source table)
My users access my reportserver interactively, scheduling anything is not an
option.
For higher analysis, my olap cubes are ready.
thanks for your feedback.
Jerome.
Hi Jerome:
I have some kind of "rule". Just make a partition for each 1 GB of data.
Or doing it for a year, would be great. If you need more granularity, give
it a try to month partitioning.
Tell me if you need some help on this
Sincerely
Alejandro Leguizamo
MVP SQL Server
Colombia
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:uwuxtzxzEHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have to plan a datawarehouse structure where the primary reporting usage
> is to list detailed information about customers.
> And also, we have OLAP cube for analysis purpose.
> I'll have 100 000 customers and a fact table containing between 35 to
> 45millions of rows by year. (we also have 2 other fact table with 5 to
> 6millions of rows by year)
> Generally, this fact table is filtered for a particular organizational
> unit and for data in 1 year. (for report generation using report server)
> So, I plan to partition my fact table by organizational unit and by year.
> But I have 180 units.
> Does the partitioning will works fine with 180 * 5 years = 900 tables?
> on this article:
> http://msdn.microsoft.com/library/de...itionsindw.htm
> there is a note that the maximum number of tables is 256.
> But the performance gain can be very high!
> The estimated size of the DW is 10gb / year (maybe more with additional
> indexes)
> My DTS package is ready to support partioning table loading. (the package
> automatically create the new table, indexes and update the view for each
> detected partition in the staging source table)
> My users access my reportserver interactively, scheduling anything is not
> an option.
> For higher analysis, my olap cubes are ready.
> thanks for your feedback.
> Jerome.
>
>
|||but does SQL Server support 500 tables in a partitioned view?
I don't need help about this, I just want to plan correctly.
and I don't want month partition but only year + organizational unit
Because I don't do sum or count aggregation in SQL (or just a little sum
compared of what my cube provide).
Generally my reports contains SQL statement like this:
* Last kown value at a specific date (subquery required) (by customer)
* events which start before and end after a specific date (between
statement) (by customer)
Its the reason of not using monthly partitions, because I never know when
these dates appear in the database.
"Alejo Leguizamo (MVP SQL)" <SQL@.sql.sql> a crit dans le message de news:
%23thX4VC0EHA.1204@.TK2MSFTNGP10.phx.gbl...
> Hi Jerome:
> I have some kind of "rule". Just make a partition for each 1 GB of data.
> Or doing it for a year, would be great. If you need more granularity, give
> it a try to month partitioning.
> Tell me if you need some help on this
> Sincerely
>
> --
> Alejandro Leguizamo
> MVP SQL Server
> Colombia
> "Jj" <willgart@.BBBhotmailAAA.com> wrote in message
> news:uwuxtzxzEHA.3336@.TK2MSFTNGP11.phx.gbl...
>
|||Jerome,
Views are based on select statements. A select statement can have a max of
256 tables in the From clause. So the answer to your specific question is
no.
Danny
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:e1ghnJD0EHA.2624@.TK2MSFTNGP11.phx.gbl...
> but does SQL Server support 500 tables in a partitioned view?
> I don't need help about this, I just want to plan correctly.
> and I don't want month partition but only year + organizational unit
> Because I don't do sum or count aggregation in SQL (or just a little sum
> compared of what my cube provide).
> Generally my reports contains SQL statement like this:
> * Last kown value at a specific date (subquery required) (by customer)
> * events which start before and end after a specific date (between
> statement) (by customer)
> Its the reason of not using monthly partitions, because I never know when
> these dates appear in the database.
> "Alejo Leguizamo (MVP SQL)" <SQL@.sql.sql> a crit dans le message de news:
> %23thX4VC0EHA.1204@.TK2MSFTNGP10.phx.gbl...
>
|||
sniff
I think I'll do this: partition by organization for the current year and by
year for the history... does this works in a partitioned view?
"Danny" <istdrs@.flash.net> a crit dans le message de news:
7Lkod.23022$Rf1.15232@.newssvr19.news.prodigy.com.. .
> Jerome,
> Views are based on select statements. A select statement can have a max
> of 256 tables in the From clause. So the answer to your specific question
> is no.
> Danny
> "Jj" <willgart@.BBBhotmailAAA.com> wrote in message
> news:e1ghnJD0EHA.2624@.TK2MSFTNGP11.phx.gbl...
>
|||The primary key of the underlying tables in the view must be the same. For
this to work, you will have to query current and history separately with
each haing its own view.
Danny
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:uKoQZzP0EHA.1932@.TK2MSFTNGP09.phx.gbl...
>
> sniff
> I think I'll do this: partition by organization for the current year and
> by year for the history... does this works in a partitioned view?
> "Danny" <istdrs@.flash.net> a crit dans le message de news:
> 7Lkod.23022$Rf1.15232@.newssvr19.news.prodigy.com.. .
>
I have to plan a datawarehouse structure where the primary reporting usage
is to list detailed information about customers.
And also, we have OLAP cube for analysis purpose.
I'll have 100 000 customers and a fact table containing between 35 to
45millions of rows by year. (we also have 2 other fact table with 5 to
6millions of rows by year)
Generally, this fact table is filtered for a particular organizational unit
and for data in 1 year. (for report generation using report server)
So, I plan to partition my fact table by organizational unit and by year.
But I have 180 units.
Does the partitioning will works fine with 180 * 5 years = 900 tables?
on this article:
http://msdn.microsoft.com/library/de...itionsindw.htm
there is a note that the maximum number of tables is 256.
But the performance gain can be very high!
The estimated size of the DW is 10gb / year (maybe more with additional
indexes)
My DTS package is ready to support partioning table loading. (the package
automatically create the new table, indexes and update the view for each
detected partition in the staging source table)
My users access my reportserver interactively, scheduling anything is not an
option.
For higher analysis, my olap cubes are ready.
thanks for your feedback.
Jerome.
Hi Jerome:
I have some kind of "rule". Just make a partition for each 1 GB of data.
Or doing it for a year, would be great. If you need more granularity, give
it a try to month partitioning.
Tell me if you need some help on this
Sincerely
Alejandro Leguizamo
MVP SQL Server
Colombia
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:uwuxtzxzEHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have to plan a datawarehouse structure where the primary reporting usage
> is to list detailed information about customers.
> And also, we have OLAP cube for analysis purpose.
> I'll have 100 000 customers and a fact table containing between 35 to
> 45millions of rows by year. (we also have 2 other fact table with 5 to
> 6millions of rows by year)
> Generally, this fact table is filtered for a particular organizational
> unit and for data in 1 year. (for report generation using report server)
> So, I plan to partition my fact table by organizational unit and by year.
> But I have 180 units.
> Does the partitioning will works fine with 180 * 5 years = 900 tables?
> on this article:
> http://msdn.microsoft.com/library/de...itionsindw.htm
> there is a note that the maximum number of tables is 256.
> But the performance gain can be very high!
> The estimated size of the DW is 10gb / year (maybe more with additional
> indexes)
> My DTS package is ready to support partioning table loading. (the package
> automatically create the new table, indexes and update the view for each
> detected partition in the staging source table)
> My users access my reportserver interactively, scheduling anything is not
> an option.
> For higher analysis, my olap cubes are ready.
> thanks for your feedback.
> Jerome.
>
>
|||but does SQL Server support 500 tables in a partitioned view?
I don't need help about this, I just want to plan correctly.
and I don't want month partition but only year + organizational unit
Because I don't do sum or count aggregation in SQL (or just a little sum
compared of what my cube provide).
Generally my reports contains SQL statement like this:
* Last kown value at a specific date (subquery required) (by customer)
* events which start before and end after a specific date (between
statement) (by customer)
Its the reason of not using monthly partitions, because I never know when
these dates appear in the database.
"Alejo Leguizamo (MVP SQL)" <SQL@.sql.sql> a crit dans le message de news:
%23thX4VC0EHA.1204@.TK2MSFTNGP10.phx.gbl...
> Hi Jerome:
> I have some kind of "rule". Just make a partition for each 1 GB of data.
> Or doing it for a year, would be great. If you need more granularity, give
> it a try to month partitioning.
> Tell me if you need some help on this
> Sincerely
>
> --
> Alejandro Leguizamo
> MVP SQL Server
> Colombia
> "Jj" <willgart@.BBBhotmailAAA.com> wrote in message
> news:uwuxtzxzEHA.3336@.TK2MSFTNGP11.phx.gbl...
>
|||Jerome,
Views are based on select statements. A select statement can have a max of
256 tables in the From clause. So the answer to your specific question is
no.
Danny
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:e1ghnJD0EHA.2624@.TK2MSFTNGP11.phx.gbl...
> but does SQL Server support 500 tables in a partitioned view?
> I don't need help about this, I just want to plan correctly.
> and I don't want month partition but only year + organizational unit
> Because I don't do sum or count aggregation in SQL (or just a little sum
> compared of what my cube provide).
> Generally my reports contains SQL statement like this:
> * Last kown value at a specific date (subquery required) (by customer)
> * events which start before and end after a specific date (between
> statement) (by customer)
> Its the reason of not using monthly partitions, because I never know when
> these dates appear in the database.
> "Alejo Leguizamo (MVP SQL)" <SQL@.sql.sql> a crit dans le message de news:
> %23thX4VC0EHA.1204@.TK2MSFTNGP10.phx.gbl...
>
|||
sniff
I think I'll do this: partition by organization for the current year and by
year for the history... does this works in a partitioned view?
"Danny" <istdrs@.flash.net> a crit dans le message de news:
7Lkod.23022$Rf1.15232@.newssvr19.news.prodigy.com.. .
> Jerome,
> Views are based on select statements. A select statement can have a max
> of 256 tables in the From clause. So the answer to your specific question
> is no.
> Danny
> "Jj" <willgart@.BBBhotmailAAA.com> wrote in message
> news:e1ghnJD0EHA.2624@.TK2MSFTNGP11.phx.gbl...
>
|||The primary key of the underlying tables in the view must be the same. For
this to work, you will have to query current and history separately with
each haing its own view.
Danny
"Jj" <willgart@.BBBhotmailAAA.com> wrote in message
news:uKoQZzP0EHA.1932@.TK2MSFTNGP09.phx.gbl...
>
> sniff
> I think I'll do this: partition by organization for the current year and
> by year for the history... does this works in a partitioned view?
> "Danny" <istdrs@.flash.net> a crit dans le message de news:
> 7Lkod.23022$Rf1.15232@.newssvr19.news.prodigy.com.. .
>
Friday, March 9, 2012
Parameters in SSRS with OLAP
Hi - I have a report that uses an OLAP cube. I cannot figure out how to pass
parameters into the report using URL. I've tried setting the parameter to
the value I desire, but that doesn't work. Here's an example:
http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
When I look at how OLAP passes parameters into reports, it's not the same as
when I use straight SQL tables. So I tried:
http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
but then I get an error message saying that the text is too long. Any help
would be appreciated.What is the MDX of the statement you are trying to execute based on the
parameter?
This has to be set up as a concatenated string in the DS for the report.
Chris E
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:2582B5B0-C2AE-4327-8A66-FECA58B19754@.microsoft.com...
> Hi - I have a report that uses an OLAP cube. I cannot figure out how to
> pass
> parameters into the report using URL. I've tried setting the parameter to
> the value I desire, but that doesn't work. Here's an example:
> http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
> When I look at how OLAP passes parameters into reports, it's not the same
> as
> when I use straight SQL tables. So I tried:
> http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
> but then I get an error message saying that the text is too long. Any help
> would be appreciated.
>|||Thanks for your response, Chris. The MDX statement is:
SELECT NON EMPTY { [Measures].[Responses], [Measures].[Quantity],
[Measures].[Total Cost], [Measures].[Revenue] } ON COLUMNS, NON EMPTY { ([Dim
Expire Group].[Dim Expire Group].[Dim Expire Group].ALLMEMBERS * [Dim
Notice].[Dim Notice].[Dim Notice].ALLMEMBERS * [Dim Notice].[Notice
Order].[Notice Order].ALLMEMBERS * [Dim YOF].[YOF Name].[YOF Name].ALLMEMBERS
* [Dim YOF].[YOF Order].[YOF Order].ALLMEMBERS * [Dim HPC].[HPC Id1].[HPC
Id1].ALLMEMBERS * [Dim HPC].[HPC Name1].[HPC Name1].ALLMEMBERS * [Dim
HPC].[HPC Order1].[HPC Order1].ALLMEMBERS * [Dim YOF].[Dim YOF].[Dim
YOF].ALLMEMBERS * [Dim Package].[Package Type Id].[Package Type
Id].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON
ROWS FROM ( SELECT ( STRTOSET(@.DimHPCHPCName, CONSTRAINED) ) ON COLUMNS FROM
( SELECT ( STRTOSET(@.DimExpireGroupDimExpireGroup, CONSTRAINED) ) ON COLUMNS
FROM ( SELECT ( STRTOSET(@.DimPackagePackageTypeId, CONSTRAINED) ) ON COLUMNS
FROM ( SELECT ( STRTOSET(@.DimProgramDimProgram, CONSTRAINED) ) ON COLUMNS
FROM [FactSourceCode])))) WHERE ( IIF( STRTOSET(@.DimProgramDimProgram,
CONSTRAINED).Count = 1, STRTOSET(@.DimProgramDimProgram, CONSTRAINED), [Dim
Program].[Dim Program].currentmember ) ) CELL PROPERTIES VALUE, BACK_COLOR,
FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
I pass several parameters into the statement. I thought I'd figured it out
by using the codes that represent the [, ] and &. But I'm still getting the
same issue when it tries to pass the parameter in the URL.
"Chris" wrote:
> What is the MDX of the statement you are trying to execute based on the
> parameter?
> This has to be set up as a concatenated string in the DS for the report.
> Chris E
> "Jim" <Jim@.discussions.microsoft.com> wrote in message
> news:2582B5B0-C2AE-4327-8A66-FECA58B19754@.microsoft.com...
> > Hi - I have a report that uses an OLAP cube. I cannot figure out how to
> > pass
> > parameters into the report using URL. I've tried setting the parameter to
> > the value I desire, but that doesn't work. Here's an example:
> >
> > http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
> >
> > When I look at how OLAP passes parameters into reports, it's not the same
> > as
> > when I use straight SQL tables. So I tried:
> >
> > http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
> >
> > but then I get an error message saying that the text is too long. Any help
> > would be appreciated.
> >
>
>|||I had a similar problem. My solve was:
the konfiguration of report paramters must set
available evaluates = not asked
and
standard value = zero
then it should function with the parameters [DimParameter].[MEMBER].[301]
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com|||I had a similar problem. My solve was:
the konfiguration of report paramters must set
available value = not asked
and
standard value = zero
then it should function with the parameters [DimParameter].[MEMBER].[301]
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
parameters into the report using URL. I've tried setting the parameter to
the value I desire, but that doesn't work. Here's an example:
http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
When I look at how OLAP passes parameters into reports, it's not the same as
when I use straight SQL tables. So I tried:
http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
but then I get an error message saying that the text is too long. Any help
would be appreciated.What is the MDX of the statement you are trying to execute based on the
parameter?
This has to be set up as a concatenated string in the DS for the report.
Chris E
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:2582B5B0-C2AE-4327-8A66-FECA58B19754@.microsoft.com...
> Hi - I have a report that uses an OLAP cube. I cannot figure out how to
> pass
> parameters into the report using URL. I've tried setting the parameter to
> the value I desire, but that doesn't work. Here's an example:
> http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
> When I look at how OLAP passes parameters into reports, it's not the same
> as
> when I use straight SQL tables. So I tried:
> http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
> but then I get an error message saying that the text is too long. Any help
> would be appreciated.
>|||Thanks for your response, Chris. The MDX statement is:
SELECT NON EMPTY { [Measures].[Responses], [Measures].[Quantity],
[Measures].[Total Cost], [Measures].[Revenue] } ON COLUMNS, NON EMPTY { ([Dim
Expire Group].[Dim Expire Group].[Dim Expire Group].ALLMEMBERS * [Dim
Notice].[Dim Notice].[Dim Notice].ALLMEMBERS * [Dim Notice].[Notice
Order].[Notice Order].ALLMEMBERS * [Dim YOF].[YOF Name].[YOF Name].ALLMEMBERS
* [Dim YOF].[YOF Order].[YOF Order].ALLMEMBERS * [Dim HPC].[HPC Id1].[HPC
Id1].ALLMEMBERS * [Dim HPC].[HPC Name1].[HPC Name1].ALLMEMBERS * [Dim
HPC].[HPC Order1].[HPC Order1].ALLMEMBERS * [Dim YOF].[Dim YOF].[Dim
YOF].ALLMEMBERS * [Dim Package].[Package Type Id].[Package Type
Id].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON
ROWS FROM ( SELECT ( STRTOSET(@.DimHPCHPCName, CONSTRAINED) ) ON COLUMNS FROM
( SELECT ( STRTOSET(@.DimExpireGroupDimExpireGroup, CONSTRAINED) ) ON COLUMNS
FROM ( SELECT ( STRTOSET(@.DimPackagePackageTypeId, CONSTRAINED) ) ON COLUMNS
FROM ( SELECT ( STRTOSET(@.DimProgramDimProgram, CONSTRAINED) ) ON COLUMNS
FROM [FactSourceCode])))) WHERE ( IIF( STRTOSET(@.DimProgramDimProgram,
CONSTRAINED).Count = 1, STRTOSET(@.DimProgramDimProgram, CONSTRAINED), [Dim
Program].[Dim Program].currentmember ) ) CELL PROPERTIES VALUE, BACK_COLOR,
FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
I pass several parameters into the statement. I thought I'd figured it out
by using the codes that represent the [, ] and &. But I'm still getting the
same issue when it tries to pass the parameter in the URL.
"Chris" wrote:
> What is the MDX of the statement you are trying to execute based on the
> parameter?
> This has to be set up as a concatenated string in the DS for the report.
> Chris E
> "Jim" <Jim@.discussions.microsoft.com> wrote in message
> news:2582B5B0-C2AE-4327-8A66-FECA58B19754@.microsoft.com...
> > Hi - I have a report that uses an OLAP cube. I cannot figure out how to
> > pass
> > parameters into the report using URL. I've tried setting the parameter to
> > the value I desire, but that doesn't work. Here's an example:
> >
> > http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
> >
> > When I look at how OLAP passes parameters into reports, it's not the same
> > as
> > when I use straight SQL tables. So I tried:
> >
> > http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
> >
> > but then I get an error message saying that the text is too long. Any help
> > would be appreciated.
> >
>
>|||I had a similar problem. My solve was:
the konfiguration of report paramters must set
available evaluates = not asked
and
standard value = zero
then it should function with the parameters [DimParameter].[MEMBER].[301]
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com|||I had a similar problem. My solve was:
the konfiguration of report paramters must set
available value = not asked
and
standard value = zero
then it should function with the parameters [DimParameter].[MEMBER].[301]
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
Saturday, February 25, 2012
Parameters - get last minus one
I have a list of parameters, and they are months. This list is dynamic, and
is based on a query to an OLAP cube.
I want my default parameter to be the last month minus one, so that when the
last month is December, I want to have November as default.
How can I do this?
All help appreciated!
Kaisa M. Lindahljust use other query to get max(month),then use the result to parameter's
default value
"Kaisa M. Lindahl" <kaisaml@.hotmail.com> дÈëÏûÏ¢
news:#sYiAa61EHA.4004@.tk2msftngp13.phx.gbl...
> I have a list of parameters, and they are months. This list is dynamic,
and
> is based on a query to an OLAP cube.
> I want my default parameter to be the last month minus one, so that when
the
> last month is December, I want to have November as default.
> How can I do this?
> All help appreciated!
> Kaisa M. Lindahl
>
is based on a query to an OLAP cube.
I want my default parameter to be the last month minus one, so that when the
last month is December, I want to have November as default.
How can I do this?
All help appreciated!
Kaisa M. Lindahljust use other query to get max(month),then use the result to parameter's
default value
"Kaisa M. Lindahl" <kaisaml@.hotmail.com> дÈëÏûÏ¢
news:#sYiAa61EHA.4004@.tk2msftngp13.phx.gbl...
> I have a list of parameters, and they are months. This list is dynamic,
and
> is based on a query to an OLAP cube.
> I want my default parameter to be the last month minus one, so that when
the
> last month is December, I want to have November as default.
> How can I do this?
> All help appreciated!
> Kaisa M. Lindahl
>
Parameters
Hi !
How come i pass olap parameter to my subreport?
I have two reports and i'd like link these reports by parameters, but when a
put parameter to link the value doen't pass to subreport.
I use SSAS 2005 and my parameters are dimension of my cube.
Help me !!!!
Thanks.
--
MattosCreate a custom member in your "parent" report. Example:
If you had the ReportDate attribute of the [Time] dimension in your report
and it needed to be passed to the sub-report, you'd create a custom member
with the definition
'[Time].[ReportDate].CurrentMember.UniqueName'
This would return something like
'[Time].[ReportDate].&[2006-05-26T00:00:00]'.
When you've added the sub-report, make sure you set up the parameters for it
too. They can be either parameters in the primary report or they can be
field values.
"André Mattos" <AndrMattos@.discussions.microsoft.com> wrote in message
news:3AD0B66F-FF85-4A76-A615-3A4B033B053C@.microsoft.com...
> Hi !
> How come i pass olap parameter to my subreport?
> I have two reports and i'd like link these reports by parameters, but when
> a
> put parameter to link the value doen't pass to subreport.
> I use SSAS 2005 and my parameters are dimension of my cube.
> Help me !!!!
> Thanks.
> --
> Mattos|||Tim,
Thanks, now work well.
André Mattos
--
Mattos
"Tim Dot NoSpam" wrote:
> Create a custom member in your "parent" report. Example:
> If you had the ReportDate attribute of the [Time] dimension in your report
> and it needed to be passed to the sub-report, you'd create a custom member
> with the definition
> '[Time].[ReportDate].CurrentMember.UniqueName'
> This would return something like
> '[Time].[ReportDate].&[2006-05-26T00:00:00]'.
> When you've added the sub-report, make sure you set up the parameters for it
> too. They can be either parameters in the primary report or they can be
> field values.
>
> "André Mattos" <AndrMattos@.discussions.microsoft.com> wrote in message
> news:3AD0B66F-FF85-4A76-A615-3A4B033B053C@.microsoft.com...
> > Hi !
> >
> > How come i pass olap parameter to my subreport?
> >
> > I have two reports and i'd like link these reports by parameters, but when
> > a
> > put parameter to link the value doen't pass to subreport.
> >
> > I use SSAS 2005 and my parameters are dimension of my cube.
> >
> > Help me !!!!
> >
> > Thanks.
> > --
> > Mattos
>
>
How come i pass olap parameter to my subreport?
I have two reports and i'd like link these reports by parameters, but when a
put parameter to link the value doen't pass to subreport.
I use SSAS 2005 and my parameters are dimension of my cube.
Help me !!!!
Thanks.
--
MattosCreate a custom member in your "parent" report. Example:
If you had the ReportDate attribute of the [Time] dimension in your report
and it needed to be passed to the sub-report, you'd create a custom member
with the definition
'[Time].[ReportDate].CurrentMember.UniqueName'
This would return something like
'[Time].[ReportDate].&[2006-05-26T00:00:00]'.
When you've added the sub-report, make sure you set up the parameters for it
too. They can be either parameters in the primary report or they can be
field values.
"André Mattos" <AndrMattos@.discussions.microsoft.com> wrote in message
news:3AD0B66F-FF85-4A76-A615-3A4B033B053C@.microsoft.com...
> Hi !
> How come i pass olap parameter to my subreport?
> I have two reports and i'd like link these reports by parameters, but when
> a
> put parameter to link the value doen't pass to subreport.
> I use SSAS 2005 and my parameters are dimension of my cube.
> Help me !!!!
> Thanks.
> --
> Mattos|||Tim,
Thanks, now work well.
André Mattos
--
Mattos
"Tim Dot NoSpam" wrote:
> Create a custom member in your "parent" report. Example:
> If you had the ReportDate attribute of the [Time] dimension in your report
> and it needed to be passed to the sub-report, you'd create a custom member
> with the definition
> '[Time].[ReportDate].CurrentMember.UniqueName'
> This would return something like
> '[Time].[ReportDate].&[2006-05-26T00:00:00]'.
> When you've added the sub-report, make sure you set up the parameters for it
> too. They can be either parameters in the primary report or they can be
> field values.
>
> "André Mattos" <AndrMattos@.discussions.microsoft.com> wrote in message
> news:3AD0B66F-FF85-4A76-A615-3A4B033B053C@.microsoft.com...
> > Hi !
> >
> > How come i pass olap parameter to my subreport?
> >
> > I have two reports and i'd like link these reports by parameters, but when
> > a
> > put parameter to link the value doen't pass to subreport.
> >
> > I use SSAS 2005 and my parameters are dimension of my cube.
> >
> > Help me !!!!
> >
> > Thanks.
> > --
> > Mattos
>
>
Subscribe to:
Posts (Atom)