Bug: default value showing as query based when it is not (report m

I have a report which uses a query to populate a parameter.
The default value is not queried, this is just set to "=1".
When the report is deployed, the parameter in report manager is showing as
'query based' which is wrong.
This is a pain in the ass as when I try linking to this report, I am not
able to set the value to something else.If you use a query to specify a range of parameters then it seems to show
default as 'query based' in the report manager.
What I have discovered is that if you change something to do with the
parameters on the report and redeploy, you can pick up the changes in the
linked report by repointing the linked report at the same report, this forces
some kind of refresh to occur and although very annoying, is easier than
recreating the linked report.
<despair>Thanks to MS for providing a UI of such high quality.</despair>
"adolf garlic" wrote:
> I have a report which uses a query to populate a parameter.
> The default value is not queried, this is just set to "=1".
> When the report is deployed, the parameter in report manager is showing as
> 'query based' which is wrong.
> This is a pain in the ass as when I try linking to this report, I am not
> able to set the value to something else.

Browsing Cube

Hi,

I have created, populate and processed a cube successfully and can also browse it successfully on one server. But when I deploy this cube to another server I can create, populate and process the cube sucessfully but when I go to browse the cube through SQL Management Studio I recive the following error:

The query could not be processed: o OLE DB error: OLE DB or ODBC error: You do not have permission to run 'SP_TRACE_CREATE'.; 42000.

I have checked the security and it all appears to be the same, I am using the domain administrator on both servers.

Have you any idea what my issue might be?

Your help will be greatly appreciated.

Cheers,

Hi,

I resolved this issue myself and am position what my resolution so that i may hopefully help someone else if they are to encounter the same problem.

Resolution:

I set the authentication of the datasources being used by the cube to SQL authentication and then used the SQL server 'sa' account as the user.

|||This would imply that you are using ROLAP or HOLAP storage. You should not need to use the "sa" account. A user with db_datareader rights should be enough. The "sa" user has too many rights and really should not be used for anything other than administrative tasks.|||

Hi Darren,

All dimensions of the cube are using plain MOLAP and the cube itself is using plain MOLAP also. If you have any suggestions on how I could browse the cube with using 'sa' as the datasources user then that would be great as I also think as you mentioned that 'sa' should only be used for administration purposes.

Cheers,

|||

MOLAP storage only needs a SQL connection at processing time. When you browse it does not need a connection to the relational source. You could try using SQL Profiler to see what is going on. Do you have pro-active caching or something like that configured?

Browsing Cube

Hi,

I have created, populate and processed a cube successfully and can also browse it successfully on one server. But when I deploy this cube to another server I can create, populate and process the cube sucessfully but when I go to browse the cube through SQL Management Studio I recive the following error:

The query could not be processed: o OLE DB error: OLE DB or ODBC error: You do not have permission to run 'SP_TRACE_CREATE'.; 42000.

I have checked the security and it all appears to be the same, I am using the domain administrator on both servers.

Have you any idea what my issue might be?

Your help will be greatly appreciated.

Cheers,

Hi,

I resolved this issue myself and am position what my resolution so that i may hopefully help someone else if they are to encounter the same problem.

Resolution:

I set the authentication of the datasources being used by the cube to SQL authentication and then used the SQL server 'sa' account as the user.

|||This would imply that you are using ROLAP or HOLAP storage. You should not need to use the "sa" account. A user with db_datareader rights should be enough. The "sa" user has too many rights and really should not be used for anything other than administrative tasks.|||

Hi Darren,

All dimensions of the cube are using plain MOLAP and the cube itself is using plain MOLAP also. If you have any suggestions on how I could browse the cube with using 'sa' as the datasources user then that would be great as I also think as you mentioned that 'sa' should only be used for administration purposes.

Cheers,

|||

MOLAP storage only needs a SQL connection at processing time. When you browse it does not need a connection to the relational source. You could try using SQL Profiler to see what is going on. Do you have pro-active caching or something like that configured?