![]() ![]() They will be created in a similar manner as described above. It is left up to the reader to create the ‘Number of doors’ and the ‘Make’ parameters. Note that we have created a ‘Color’ parameter which is highlighted in blue. Fear not, we shall be returning to this parameter in a few minutes.Īt this point in time your screen will appear as follows: The astute reader will note that I have set the parameter name to ‘Color’, the prompt to ‘Color’, and more importantly the ‘Allow multiple values’ box has been checked.įor the time being I am just going to say ‘OK’ and close the parameter selection box. ![]() ![]() The ‘Report Parameter Properties’ screen is then shown. I right click on the Parameters folder (in the upper left hand portion of the screen dump above) and choose ‘Add Parameter’. Should yours not be visible, then simply click on the ‘View’ Tab of SSDT and the option to show the ‘Report Data’ window may be found there. In order to create a parameter, we must ensure that our ‘Report Data’ window is visible. This data will then be reflected in a data matrix. These parameters will permit the user to pass ‘desired’ criteria to a stored procedure that will utilize these criteria to pull the correct data from the database table(s) and return the data to the report. Setting our report parameters (Color, Number of Doors, Make)Īs we want our report to be a flexible as possible, we must create a few ‘user selection’ parameters. I first want to increase the size of our drawing surface (see below). We are now ready to create our first report. I have taken the liberty completing the name of the connection string and point the string to the correct SQL Server instance and database. By clicking ‘Edit’ we arrive at the ‘Connection Properties’ data entry screen (see below). Note that I have given the data source a name (see above) and the only step left is to define the ‘connection string’ to our database (where our report data resides). The ‘Shared Data Source Properties’ data entry screen is then displayed. It should be noted from the outset that this data source (as it is shared) is for all intents and purposes a ‘GLOBAL’ data source. I choose ‘Add New Data Source’ from the context menu (see above). I right click on ‘Shared Data Sources’ and the following context menu is displayed (see below top right). The report will be using the ‘water’ /data thus it is necessary to define where that ‘water’ / data resides. We must now create a ‘Shared Data Source’ to access our data.Ī data source may be likened to a ‘water tap’ on a house. The click Add.Īs the reader will note above, we now have a drawing surface, and an area to define and to create datasets parameters (upper left). We choose the option ‘Report’ and give our report a name: ‘SQLShackCars’. The ‘new report’ menu is then brought up for you to see. We first need to create a brand new ‘report’.īy right clicking on the Reports folder on the ‘Solution Explorer we see the context menu (see above). We click OK to arrive at our drawing surface. The project may be created in any directory that is convenient to you. Opening SQL Server Data Tools (hence forward referred to as SSDT) we begin by creating a Reporting Services Project call ‘Cars’. The screen shot below is a sample of the final report AND we are going to look at the steps necessary to create this report. Knowing this, I decided (where possible) to attempt to construct the reports so as to enable the firm to do their ‘what if’ scenarios with a minimal amount of time and effort. The one request that I had received (from this client) was to ensure that the finished reports were as ‘all encompassing’ as possible, as they wanted to conduct a considerable amount of Business Analytics, via the reports. A few months ago, I was working on a few SQL Server reports for a client. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |