Analysis Services & Default Value

Is it possible to define a default value for each a parameter also in a dataset?

I have a dataset with a parameter from the dimension Time. I would like to change the default value from the parameter. I tried to create a dataset to get the current year unique name, but if I set it in the parameter dialog it does not recognize the value.

I have a dataset in a report with the parameter Year from the dimension Time.

In the dataset I have to select a default value for the parameter. There is no other option.

In the reports parameters list I can specify a default value. This is not recognized, if it does not mach previous one.

Is it possible to set the default value of such a parameter to the current year value?

Analysis Service Ports

SQL 2005 AS installed on a Cluster.
We are using a named instance and only one currently exists. MS White paper
reads: The default instance listens on port 2383, while named instances are
dynamically allocated. This behavior can be changed by explicitly assigning a
port to either the default or named instance of SSAS. If the value for Port
is 0, the default behavior described above is achieved. Otherwise, the value
is treated as an absolute (static) port number to use for the specified
instance.
I have modifed the Server PORT property, on the named instance (a default
instance does not exist) to listen on port 2382 and have added a rule to our
firewall to allow this traffic. However, AS continues to listen on port 2383.
Does anyone have any experience on this and how to change it.
Is there a range of ports I can tell our network team to open?
I am not sure on SQL 2005 but in SQL 2000 you need to start the service
again to take the effect of new port numbers...
Zaki.
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:6A9E45E1-E591-4086-B8A3-A5A1556BFFDC@.microsoft.com...
> SQL 2005 AS installed on a Cluster.
> We are using a named instance and only one currently exists. MS White
paper
> reads: The default instance listens on port 2383, while named instances
are
> dynamically allocated. This behavior can be changed by explicitly
assigning a
> port to either the default or named instance of SSAS. If the value for
Port
> is 0, the default behavior described above is achieved. Otherwise, the
value
> is treated as an absolute (static) port number to use for the specified
> instance.
> I have modifed the Server PORT property, on the named instance (a default
> instance does not exist) to listen on port 2382 and have added a rule to
our
> firewall to allow this traffic. However, AS continues to listen on port
2383.
> Does anyone have any experience on this and how to change it.
> Is there a range of ports I can tell our network team to open?
|||I have restarted the service multiple times and it continues to listen on
this port.
"Zakiuddin Mohammed" wrote:

> I am not sure on SQL 2005 but in SQL 2000 you need to start the service
> again to take the effect of new port numbers...
> Zaki.
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:6A9E45E1-E591-4086-B8A3-A5A1556BFFDC@.microsoft.com...
> paper
> are
> assigning a
> Port
> value
> our
> 2383.
>
>

An attempt to attach an auto-named database for file

I build a WebApp which i use the default DataBase that come with the App_Data folder.

I have Users and roles into that folder with all my tables regarding my new App.

Why i cant make it work under IIS on my webserver ? When i open it with Visual Studio everything works but outside of it nothing.

An attempt to attach an auto-named database for file c:\inetpub\wwwroot\Survey\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf;

I look arround and cant find a thing on how to fix my issue. I try deleting the Folder under my User Account for SQL Express and nothing happend.

Make sure your IIS account (ASPNET or NETWORK SERVICE) has read&write permission on the folder where the database file locates.|||Yes i did that ! even uers have modify to it. under that folder !|||

Im still looking for help arround here !

anybody fix the issue?

|||

It is not working because IIS is not the place to store database files, you store those in the data subfolder of Microsoft SQL Server in programs. You can modify the code in the thread below for your use. You may need to start with the trail version of SQL Server and later buy the developer edition it is under $40 on the web. Hope this helps.

http://forums.asp.net/thread/977493.aspx

Always showing the parameter input area.

Greetings,

Is there a way to force the parameter input area to always show even when default values are specified? I want to always display the parameter area even when I set initial parameters.

Thanks

--|||

The strange thing is in one report I have a date parameter set to a default value of =Today() and in that report the parameter input area is always visible.

For a test I added a kludge parameter to the other report as a date and the input area is still in a collapsed state.

It must be the way the other parameters are processed.

|||

It's odd that your parameters area doesn't display just because the parameters are satisfied. Is this a drillthrough target by any chance? Drillthrough targets will have their parameters areas collapsed, since their parameterization is implied by the drillthrough parent.

The use of an expression for the default value ("=Today()) may short-circuit this, such that the viewer doesn't know ahead of time if the expression for the default value will evaluate. In that case, the viewer may just decide to show the parameters area in case the expression doesn't evaluate to a valid default value.

What build of Report Server are you using? On my test servers, the drillthrough target's parameters area is collapsed, even if I use an expression for the default value.

|||

"Prompt" properties of that parameter is blank?

|||

Thanks for the reply. I have not checked the forum in a while nor have I found a workaround.

This is not a drill through report and the prompt string has been specified.

I am working with 3 parameters and only one is a prompted parameter.

P1 Integer - Internal - No available values -default value of 0 - non-prompt

P2 Integer - Hidden - No available values - default value comes from query - non prompt

P3 - String - Prompt specified - Available values from query (forces drop down list) - Default value from query - prompt

I wish for the 3rd parameter, displayed in the parameter input area, to be visible when the report renders but it's not, the whole area is collapsed.

Could it be something to do of the order or timing of parameter processing?

|||

Made progress!

When I invoke the report via the url command the parameter area is always visible.

When I invoke the report via the navigation functionality of a report item the report is rendered but the parameter area collapsed.

Still dont know why....

Always showing the parameter input area.

Greetings,

Is there a way to force the parameter input area to always show even when default values are specified? I want to always display the parameter area even when I set initial parameters.

Thanks

--|||

The strange thing is in one report I have a date parameter set to a default value of =Today() and in that report the parameter input area is always visible.

For a test I added a kludge parameter to the other report as a date and the input area is still in a collapsed state.

It must be the way the other parameters are processed.

|||

It's odd that your parameters area doesn't display just because the parameters are satisfied. Is this a drillthrough target by any chance? Drillthrough targets will have their parameters areas collapsed, since their parameterization is implied by the drillthrough parent.

The use of an expression for the default value ("=Today()) may short-circuit this, such that the viewer doesn't know ahead of time if the expression for the default value will evaluate. In that case, the viewer may just decide to show the parameters area in case the expression doesn't evaluate to a valid default value.

What build of Report Server are you using? On my test servers, the drillthrough target's parameters area is collapsed, even if I use an expression for the default value.

|||

"Prompt" properties of that parameter is blank?

|||

Thanks for the reply. I have not checked the forum in a while nor have I found a workaround.

This is not a drill through report and the prompt string has been specified.

I am working with 3 parameters and only one is a prompted parameter.

P1 Integer - Internal - No available values -default value of 0 - non-prompt

P2 Integer - Hidden - No available values - default value comes from query - non prompt

P3 - String - Prompt specified - Available values from query (forces drop down list) - Default value from query - prompt

I wish for the 3rd parameter, displayed in the parameter input area, to be visible when the report renders but it's not, the whole area is collapsed.

Could it be something to do of the order or timing of parameter processing?

|||

Made progress!

When I invoke the report via the url command the parameter area is always visible.

When I invoke the report via the navigation functionality of a report item the report is rendered but the parameter area collapsed.

Still dont know why....