Parameter selection causing screen refresh

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Reporting Services » Reporting Services » Parameter selection causing screen refresh

12 posts, Page 1 of 2

1 2 »»

Parameter selection causing screen refresh

Rate Topic

Display Mode

Topic Options

Author

Message

Jon Spink

Posted Wednesday, October 24, 2007 7:43 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, June 20, 2012 5:02 AM
Points: 530, 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.

Post #414434

dva2007

Posted Monday, December 31, 2007 5:00 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 9:05 AM
Points: 530, Visits: 1,020

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

Post #437520

Jon Spink

Posted Wednesday, January 02, 2008 2:58 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, June 20, 2012 5:02 AM
Points: 530, 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

Post #437870

Sabrina D Nelson

Posted Thursday, January 03, 2008 5:02 PM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, January 17, 2012 12:01 PM
Points: 17, Visits: 22

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

Post #438682

Jon Spink

Posted Friday, January 04, 2008 2:53 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, June 20, 2012 5:02 AM
Points: 530, 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?

Post #438823

Sabrina D Nelson

Posted Friday, January 04, 2008 8:35 AM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, January 17, 2012 12:01 PM
Points: 17, Visits: 22

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.

Post #438985

Jon Spink

Posted Friday, January 04, 2008 10:27 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, June 20, 2012 5:02 AM
Points: 530, 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?

Post #439039

Sabrina D Nelson

Posted Sunday, January 13, 2008 4:03 PM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, January 17, 2012 12:01 PM
Points: 17, Visits: 22

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.

Post #442259

Jon Spink

Posted Monday, January 14, 2008 3:41 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, June 20, 2012 5:02 AM
Points: 530, 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.

Post #442364

Sabrina D Nelson

Posted Sunday, January 20, 2008 10:52 AM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, January 17, 2012 12:01 PM
Points: 17, Visits: 22

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.

Post #445304

« Prev Topic | Next Topic »

12 posts, Page 1 of 2

1 2 »»

Permissions