Showing posts with label input. Show all posts
Showing posts with label input. Show all posts

Wednesday, March 28, 2012

Parameter missing

Hi,

I was developed the rdl report and i deployed to the server, In my report having the single input parameter When i run the report

asking parameter value and i was gave the value it was generated the report it is working fine.

Then this rdl report bind to the reportviewer control using

Report viwer tasks :

Choose Report : < Server Report>

Server Report Url:http://localhost/reportserver

Report Path : /Sales/Details

then i run the error should shown:

  • An error has occurred during report processing.
  • Query execution failed for data set 'Details'.
  • Procedure 'Usp_Details' expects parameter '@.PId', which was not supplied.

    How i pass the parameter value in reportviewer.

    Plz any one would help to me.

    regards

    kumar

    First deploy it and go to the IIS and open the Report folder and browse it.You can find your report there.Run that report.If that is working fine so some other problem was there.Do like that way if it is working so the page should work fine.

    |||

    Hi,

    Thanks for your response

    I did you told that way it is working fine and i was bind the rdl report to Reportviewer in my webpage then i ran the error should occured

    An error has occurred during report processing.

  • Query execution failed for data set 'Details'.
  • Procedure 'Usp_Details' expects parameter '@.PId', which was not supplied|||

    ptParameters[0] =
    new Microsoft.Reporting.WebForms.ReportParameter("ClientId", sessParam );

    this.ReportViewer1.ServerReport.SetParameters(RptParameters);
    this.ReportViewer1.ServerReport.Refresh();

    check this article for more infohttp://www.codeproject.com/sqlrs/ReportViewer2005.asp

    |||

    It is working fine thanks lot

    regards

    kumar

    sql
  • Monday, March 26, 2012

    Parameter Input Area on Drill Through

    Does anyone know a way to force RS to not collapse the parameter area on a drill through? I searched this forum and found some related threads but nothing that covered this.

    I have several reports where they drill through to each other and in all cases, while they pass the parameters between, the users usually want to go directly to different products or time periods within the reports. They constantly have to expand the input area every time they go to another report. This confuses a lot of them.

    Is there a setting somewhere that controls this?

    Thanks, Tim

    Sorry, this can't be changed in Report Manager or Report Server URL Access. If you were to use the VS Reporting controls in a custom app, you'd be able to do this.

    Parameter Date Format!

    Hi,

    How to control the Datetime Parameter's format, such as I need the user input Date and Time, but default, the user can only select date, but can not input the time.

    How to solve it?

    Thank you.

    Jeffers,

    You could give your users two textbox parameter for date and time entry, combine to 2 strings ( "mm/dd/yyyy" + "00:00:00" ) and use a cdate function convert to the actual datetime field.

    Ham

    Friday, March 23, 2012

    parameter area extension

    How can I extend Reporting services UI to include into input
    parameter's area TreeView control like to calendar picker ?
    Thank you in advance,
    L.Lubich,
    MCSD, Web programmerneed to write your own UI, since SSRS doesn't provide facitilites for
    changing the UI of the report.
    Amarnath
    "Lubich" wrote:
    > How can I extend Reporting services UI to include into input
    > parameter's area TreeView control like to calendar picker ?
    > Thank you in advance,
    > L.Lubich,
    > MCSD, Web programmer
    >

    Parameter & Execution plans.

    Hi all,

    I have a table TableA with few million rows. When I query TableA , the execution plans changes based on the input parameter as shown below . Why this happens ? How to resolve this ? Any inputs would be appreciated.

    SELECT * FROM TableA WHERE Column1 = 1 => SELECT -> Clustered Index Scan (100%)

    SELECT * FROM TableA WHERE Column1 = 2 => SELECT -> Clustered Index Scan (100%)

    SELECT * FROM TableA WHERE Column1 = 3 => SELECT -> Parallelism (3%) -> Clustered Index Scan (97%)

    SELECT * FROM TableA WHERE Column1 = 4 => SELECT -> Nested Loops -> Index Seek (50%) -> Clustered Index Seek (50%)

    (takes a very long time to retrieve the records)

    Thanks in advance,

    DBLearner.

    Hi DBLearner,

    SQL Server recompiles your SQL each time becuase you are running Adhoc SQL. You can either create a stored procedure or use Forced Parameterization database option (sql 2005 ONLY).

    The reason its using different access methods could be down to what STATISTICS are stored for those values. You might want to update stats and try it again.

    Jag

    |||

    what all are the indexes created on this table/column. ALso tell us the approx occurence of this column value (if its not PK).

    Madhu

    Monday, March 12, 2012

    Paging in sql 2005 using ROW_NUM()

    It seems that Row_num() function does not works with Dynamic sql having if
    blocks to check input parameters for null and sp_executesql t excute the
    query...Please help me to find a necesasry solution..
    Hari
    Can yopu post sample data + an expected result to be tested?
    "Hari" <Hari@.discussions.microsoft.com> wrote in message
    news:8CE0B2A3-4347-4983-BD35-A2B502BFFD8D@.microsoft.com...
    > It seems that Row_num() function does not works with Dynamic sql having if
    > blocks to check input parameters for null and sp_executesql t excute the
    > query...Please help me to find a necesasry solution..

    Paging in sql 2005 using ROW_NUM()

    It seems that Row_num() function does not works with Dynamic sql having if
    blocks to check input parameters for null and sp_executesql t excute the
    query...Please help me to find a necesasry solution..Hari
    Can yopu post sample data + an expected result to be tested?
    "Hari" <Hari@.discussions.microsoft.com> wrote in message
    news:8CE0B2A3-4347-4983-BD35-A2B502BFFD8D@.microsoft.com...
    > It seems that Row_num() function does not works with Dynamic sql having if
    > blocks to check input parameters for null and sp_executesql t excute the
    > query...Please help me to find a necesasry solution..|||Have you considered using key values rather than page numbers for paging?
    Using key values is significantly faster than row numbering techniques can
    ever be b/c each page query is simply an index range scan rather than having
    to materialise row numbers in a result-set simply to work out which rows
    make up page n. It also more accurately accounts for movements in the
    underlying database.
    Regards,
    Greg Linwood
    SQL Server MVP
    http://blogs.sqlserver.org.au/blogs/greg_linwood
    Benchmark your query performance
    http://www.SQLBenchmarkPro.com
    "Hari" <Hari@.discussions.microsoft.com> wrote in message
    news:8CE0B2A3-4347-4983-BD35-A2B502BFFD8D@.microsoft.com...
    > It seems that Row_num() function does not works with Dynamic sql having if
    > blocks to check input parameters for null and sp_executesql t excute the
    > query...Please help me to find a necesasry solution..

    Paging in sql 2005 using ROW_NUM()

    It seems that Row_num() function does not works with Dynamic sql having if
    blocks to check input parameters for null and sp_executesql t excute the
    query...Please help me to find a necesasry solution..Hari
    Can yopu post sample data + an expected result to be tested?
    "Hari" <Hari@.discussions.microsoft.com> wrote in message
    news:8CE0B2A3-4347-4983-BD35-A2B502BFFD8D@.microsoft.com...
    > It seems that Row_num() function does not works with Dynamic sql having if
    > blocks to check input parameters for null and sp_executesql t excute the
    > query...Please help me to find a necesasry solution..|||Have you considered using key values rather than page numbers for paging?
    Using key values is significantly faster than row numbering techniques can
    ever be b/c each page query is simply an index range scan rather than having
    to materialise row numbers in a result-set simply to work out which rows
    make up page n. It also more accurately accounts for movements in the
    underlying database.
    Regards,
    Greg Linwood
    SQL Server MVP
    http://blogs.sqlserver.org.au/blogs/greg_linwood
    Benchmark your query performance
    http://www.SQLBenchmarkPro.com
    "Hari" <Hari@.discussions.microsoft.com> wrote in message
    news:8CE0B2A3-4347-4983-BD35-A2B502BFFD8D@.microsoft.com...
    > It seems that Row_num() function does not works with Dynamic sql having if
    > blocks to check input parameters for null and sp_executesql t excute the
    > query...Please help me to find a necesasry solution..