|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 12:01 PM
Points: 2,677,
Visits: 2,273
|
|
Excellent stuff!
Have downloaded, installed, and now ready to play. Thank you for sharing these.
Kev
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, October 11, 2012 2:06 PM
Points: 28,
Visits: 78
|
|
Several points to note: 1. 2005 is different than 2008 in schema and the type of metrics available. 2008 has more information. 2. If your solution does not use a datawarehouse and goes directly to the ezecutionlog, the usage metrics are only as good as the history. The default is 60 days.
A solution exists on codeplex called sqlscrubs to extract all of that information from reporting services 2008 to drive actionable report optimization. It includes the necessary datawarehouse, ssis package and set of starter reports.
Http://scrubs.codeplex.com
.
SQLScrubs: SSRS Audit, Optimization & Management reports
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 9:09 AM
Points: 347,
Visits: 1,339
|
|
Very nice article and great job on the reports. Wasn't sure if you were aware of it at all, but with the SSRS Samples on CodePlex there is an SSIS package and Reports that you can leverage, Report Execution Log Files. Doesn't provide everything you have provided, but you might want to check it out if you haven't seen this before. The only reason that you would want this is because you will want to offload the Execution information since the default setting is to only keep 60 days of history.
There are other Report Packs available for SSRS 2005 that you can check out here on the Microsoft downloads SQL Server 2005 Report Packs.
Thanks for sharing your work. Once again very nice.
---------------------------------------------------------------------------------------- Dan English - http://denglishbi.wordpress.com
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Yesterday @ 6:54 PM
Points: 3,578,
Visits: 5,120
|
|
Thanks for sharing your work!
Best,
Kevin G. Boles SQL Server Consultant SQL MVP 2007-2012 TheSQLGuru at GMail
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Friday, July 06, 2012 10:51 AM
Points: 68,
Visits: 374
|
|
Michael, we used to fight with Develpoers on why the report has failed. Now you can see on the Subreport "ReportErrors". Now we can see who went on to give himself power to run and edit reports.
A very nice piece of Work. Especially on your introduction of how you used to take time to establish the problem, now you have made a master piece which can manifest within seconds.
I did test with SQL 2005 and it seems as if I did develop these reports on my own!!!
If possible just give me any hints about Reporting Services. I am not much concentrating on Reporting on my Work but today I have changed my mind.
Michael thanks for changing other people's minds also. I will be on Reporting from now on.
Thanks
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Tuesday, October 30, 2012 10:30 AM
Points: 49,
Visits: 529
|
|
Still can't find where I can see what the name of the stored procedure that each report uses is?
Any ideas anyone?
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, May 09, 2013 6:06 AM
Points: 27,
Visits: 161
|
|
Roger...
Typically I like developing reports with a procedure (kept within the database) and an RDL file (which executes the procedure). To make these as easy for deployment as possible to the greater audience, I embedded the query directly into the RDL file. The most simple way to view them would be to do the following:
1) Open the RDL (not in visual studio, but in the XML view. If you are not sure how to do that, just put the file somewhere, like your desktop, and double click it).
2) Search for the text string "<Query>" (do not include the double quotes - only what is inside the quotation marks).
3) You should be taken to the section in the RDL file that contains the query (some of these report have multiple queries). Just past the <DataSourceName> and <CommandText> tags begins the SQL code. That should be what you are looking for...
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 11:43 AM
Points: 31,
Visits: 44
|
|
Wonderful addition to my reporting. Easy to install and use. Thanks for sharing!
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Friday, May 17, 2013 12:22 PM
Points: 10,571,
Visits: 11,871
|
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Tuesday, October 30, 2012 10:30 AM
Points: 49,
Visits: 529
|
|
| Thanks for the reply Michael, yes that is how I do it at the moment, but it would be great if I could query all my reports and see what the stored procedure for each one was in one go .. how possible is this?
|
|
|
|