Welcome to PC Teach Me...

Free Computer Training Videos.

Although you do not need to register to access this site. Registering has its benefits. Such as:

  • Access to training material associated with the video you are watching [if applicable]
  • Automatic email updates when new training videos are available.
  • Ask for a training video.
  • Exclusive access to pose questions to me [limited availability as I am doing this for free :-)].
  • Free contribution of your own training topics, this includes referencing your videos outside of PC Teach Me.
  • Its Free!

Member Login

Lost your password?

Not a member yet? Sign Up!

By registering with this blog you are also agreeing to receive email notifications for new posts but you can unsubscribe at anytime.

25426 Registered Users
71 Number Of Articles
Free Video Tutorials (Email) Free Video Tutorials (RSS) Free Video Tutorials (Twitter) Free Video Tutorials (Flickr)

SSRS: Intro To Parameters

Part of Microsoft Reporting Services Basics

sql SSRS: Intro To ParametersSSRS: Parameters Introduction

With your SSRS report well underway, the next hurdle is ensuring your report is able to change its results depending on the criteria the user wants. You could create a myriad of different reports to offer the user choice but this becomes quite difficult to manage. It is a much better idea to have one report that has the ability to let the user filter the results the way he/she want it. This is accomplished by putting report parameters onto the report.

How to implement parameters in SSRS

For this you will need to amend the SSRS report to handle parameters, more over if you are utilising SQL to obtain the information then a SQL script alteration will also be required.
This video will show you how to create parameters and allowing users to choose from a list of options.This video is one of many SSRS tutorials on this site click here for more.

Example SSRS File

To download the example SSRSproject shown in this video please click here:

Related Posts

658 Comments

  1. bcrie says
    04 Dec 11 at 2:47pm

    [..YouTube..] Excellent explanation…Thanks…

  2. bcrie says
    04 Dec 11 at 2:47pm

    Excellent explanation…Thanks…

  3. bcrie says
    04 Dec 11 at 2:47pm

    Excellent explanation…Thanks…

  4. bcrie says
    04 Dec 11 at 2:47pm

    Excellent explanation…Thanks…

  5. Hariharan says
    05 Nov 11 at 2:38pm

    Its Very Nice you have given me a great idea for creating a report. thanks for your work

  6. PCTeachME says
    30 Aug 11 at 10:13am

    Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  7. PCTeachME says
    30 Aug 11 at 10:13am

    [..YouTube..] Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  8. PCTeachME says
    30 Aug 11 at 10:13am

    [..YouTube..] @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  9. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  10. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  11. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  12. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  13. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  14. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  15. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  16. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  17. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  18. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  19. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

  20. PCTeachME says
    30 Aug 11 at 10:13am

    @jflor98 Hi, I have not had the fortune of DB2 (I ETL to SQL first). From a quick scan on google it appears that there are several other people in the same boat. From what I have read DB2 hates SQL sending a date as a datetime field! So the way was to make the parameter a varchar. The problem then is you loose the date control off the report. Suggestion: Pass the date to a report parameter (SSRS would retain the date control) but then either code or another dataset to convert to DB2 format.

Leave a Comment

You must be logged in to post a comment.

Valid XHTML 1.0 Transitional website security