SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Parameter selection causing screen refresh


Parameter selection causing screen refresh

Author
Message
Jon Spink
Jon Spink
SSC Eights!
SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)

Group: General Forum Members
Points: 804 Visits: 945
When some parameters are selected from drop-down boxes, the screen refreshes. With users on remote links, this can cause a delay of a minute or so in between choosing parameters which is unacceptable. Does anyone know how to control this?

BTW, I discovered that with date parameters and string parameters with calculated defaults, putting these first in the parameter list avoids a lot of unnecessary screen refreshes. However, where one parameter depends on another, there doesn't seem to be any alternative.
dva2007
dva2007
SSC Eights!
SSC Eights! (946 reputation)SSC Eights! (946 reputation)SSC Eights! (946 reputation)SSC Eights! (946 reputation)SSC Eights! (946 reputation)SSC Eights! (946 reputation)SSC Eights! (946 reputation)SSC Eights! (946 reputation)

Group: General Forum Members
Points: 946 Visits: 1112
hi,

If one parameter (sub category) appears after selection of other parameter (category) then it is necessary that screen should refresh. At that time it will run your query from dataset and according to your selection it will select other data. So, if you have one parameter output depends on other then it is not possible that u can stop refresh.

Hope this helps.

Vijay
Jon Spink
Jon Spink
SSC Eights!
SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)

Group: General Forum Members
Points: 804 Visits: 945
Yes, there doesn't seem to be a way round it for 'cascading parameters'. However you can stop the screen refresh for date parameters, by setting the default value to another parameter
Sabrina D Nelson
Sabrina D Nelson
Valued Member
Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)

Group: General Forum Members
Points: 59 Visits: 37
Have you thought of storing the parameter values in a parameter table? This will decrease your query/refresh time. Even with parameters that rely on other parameters.

All of my parameters are refreshed with new values from the database nightly and are pulled from a parameter table with the basic values of ParameterName, ParameterLabel, ParameterValue. This has really increased the performance and refresh time on reports.

Sabrina
Jon Spink
Jon Spink
SSC Eights!
SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)

Group: General Forum Members
Points: 804 Visits: 945
That sounds interesting, Sabrina. How would that work say if I wanted to report on projects across the world and would be choosing continent, country and project from 3 different lists? Also, is your parameter table held locally or on the server?
Sabrina D Nelson
Sabrina D Nelson
Valued Member
Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)

Group: General Forum Members
Points: 59 Visits: 37
I have all the parameters go into a table. Example:

ParameterName ParameterLabel ParameterValue
Country Country UnitedStates
Country Country Australia
Continent Continent North America
Continent Continent Asia
Project Project SQL
Project Project Java
Manager Manager Sabrina
Manager Manager Cory

The table is on the server and the report calls the parameters through a data query (one for each parameter) to this table. The table itself is populated by a select 'Country' as parametername, 'Country' as parameterlabel, columnname as ParameterValue from table where columnname <> '' or columnname is NOT NULL order by columnname.

ParameterLabel is good to use if your SQL name for the parameter is 'computerafied'...ie not user friendly.
Jon Spink
Jon Spink
SSC Eights!
SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)

Group: General Forum Members
Points: 804 Visits: 945
Hmmm... how does this work if the user selects a continent and then expects to get a choice (in the country parameter drop-down) of only those countries in that continent? And once they've selected a country they should get a list only of those projects assigned to that country?
Sabrina D Nelson
Sabrina D Nelson
Valued Member
Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)

Group: General Forum Members
Points: 59 Visits: 37
Sorry, busy week.

Add two more columns MasterParameter and MasterParametervalue, Master Parameter would only be filled for those columns that have a master or linked parameter that determines their value.

ParameterName ParameterLabel ParameterValue MasterParameter MasterParameterValue
Country Country UnitedStates Continent North America
Country Country Great Britain Continent Europe
Country Country France Continent Europe

Then have the query look for all Country parameters where the MasterParameterValue is Europe, what ever continent ONLY.

Same idea for the project. The populatino of the parameters would be a SQL statement based on your buisness rules for the Parameter selection.
Jon Spink
Jon Spink
SSC Eights!
SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)SSC Eights! (804 reputation)

Group: General Forum Members
Points: 804 Visits: 945
You said in an earlier post: 'All of my parameters are refreshed with new values from the database nightly'. So where is your parameter list stored if not on the database itself?

Thanks.
Sabrina D Nelson
Sabrina D Nelson
Valued Member
Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)

Group: General Forum Members
Points: 59 Visits: 37
My parameters are stored on the database. They pull from stored procedures in the report that call the parameter table I described to you. I have a stored procedure that nightly complies all the parameter information into the parameter table. This way, the report is NOT asking for information from the database tables that contain ALL the information, nor is the report calling on a datamart. Just the information in the parameter table that has been pared down to ParameterName, ParameterLabel, ParameterValue, MasterParameterName, and MasterParameterValue.

The nightly stored procedure that pulls the information takes about 10 minutes to run or more depending on the UNIONs and other information being feed to the parameter table. It is a LONG stored procedure...but having my reporting set up this way has drastically reduced the delay times.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search