Showing posts with label explain. Show all posts
Showing posts with label explain. Show all posts

Friday, March 30, 2012

more on parameters...

We have a custom .net webb app front end that uses the SOAP methods for rs.
For reasons that are not important to explain, we have several different
types of parameters..we have a couple that we would like to have the user do
an external search (there are too many values to set the parameter up to run
an sp to display allowable values) so we want to create a 'search' page for
them to narrow down / search and pick an appropriate value. The SP that
supplies the report(s) needs to have a value passed to run the report (we
can't filter after the fact). My question is that no 2 databases (out of 60
+ databases) are going to have the same value(s) for these particular
parameters - but I need to set the parm up to have a default value...I
believe... . Does the default value have to be an allowable value? Or can
you put something in as a place holder or a phrase to look for in code so we
can take the neccessary next step (open search page)?
I hope I am explaining this ok...
Thanks,Its hard to unserstand. In generay you can define any default values for RS
Reports if you like. Same for SP, but I think you should be careful wit
datatype there.
Markus Pöhler
netpoint-edv gmbh
Germany
"Myles" wrote:
> We have a custom .net webb app front end that uses the SOAP methods for rs.
> For reasons that are not important to explain, we have several different
> types of parameters..we have a couple that we would like to have the user do
> an external search (there are too many values to set the parameter up to run
> an sp to display allowable values) so we want to create a 'search' page for
> them to narrow down / search and pick an appropriate value. The SP that
> supplies the report(s) needs to have a value passed to run the report (we
> can't filter after the fact). My question is that no 2 databases (out of 60
> + databases) are going to have the same value(s) for these particular
> parameters - but I need to set the parm up to have a default value...I
> believe... . Does the default value have to be an allowable value? Or can
> you put something in as a place holder or a phrase to look for in code so we
> can take the neccessary next step (open search page)?
> I hope I am explaining this ok...
>
> Thanks,

Wednesday, March 28, 2012

more empty fields

I will explain the problem as best I can(bad English, sorry)
There are 2 tables in the database, there is 1 field with the same name in both tables.
The report shows information based on this common field witch I use to filter the data.
As soon as the common field is not yet in the second table because the user has not yet placed data there with the common field the reports flips totally blank.

I hope this explanation helps, this problem bugs me for some time and I have to make more reports based on this database structure.

ThanksYou need a left outer join from the first table to the second one.

Friday, March 9, 2012

Monitoring cube aggregations.

Hi All,Can some one explain me the process of monitoring the aggregations created during the cube design are being used while running a MDX , for example aggregations are created during the design process of adventure works DW cube, I would like to verify those aggregations are being used when I fire a query against a particular measure in a measure group for which aggregations are created.Thanks

It is mentioned in Teo Lachev's book (Applied Microsoft Analysis Services p.460):

"You can use SQL Server Profiler to determine if a given query is satisfied from the cube aggregation or not. However the SQL Server Profiler won't tell you why the server has decided to use a particular aggregation. If the server didn't use aggregations, the Progess Report event will show 'Start reading data from the Partition Name partition'. Otherwise the report will say 'Start reading from the Aggregation Name aggregation'."

Hope this answers your question

Christina

|||Thanks Christina,I got the answer from your message.