|
While working on MS SQL Reporting Services, I came accross IIS Report Pack a set of 12 Sample Reports for Reporting Services.
The Microsoft SQL Server Report Pack for Internet Information Services (IIS) is a set of 12 Microsoft SQL Server 2000 Reporting Services reports that works with a sample database of information extracted from Microsoft Internet Information Services (IIS) log files.
This database can be populated with your own data using the Log Parser included with the IIS 6.0 Resource Kit.
You can also use the sample reports as templates for designing new reports.
Although the sample reports are really good in UI and concept, but it lacks the scalability to even support a small scale (low traffic) websites logs.
For this, it requires major changes at the DB level as well as in the Report Definition Files.
Since designing of MIS Reports is one of my favorite works, from the time I designed & developed MIS Reports for the India's number one SMS Service ( 8888 of Indiatimes/Times Of India ) which receives around 2 million messages a day..
I decided to make the Report Pack more scalable and usable.
To make the reports scalable enough to handle data of high traffic websites, many changes were required in the report pack which are mentioned as under:
1. Redesigning of Database
a. Added new tables to store the summary,
b. Added new Stored Procedures to insert and retrieve data from new tables,
c. Removed bugs from few already existing Stored Procedures.
2. Redesigning of Report Definition Language (RDL) files,
3. Added new Report for Response Status,
4. Created a Windows Service to execute LogParser command as a schedule task, to parse IIS Logs.
By doing this MSSQL Server Report Pack for IIS got much faster with multifold increase in Report Processing speed:
1. Less Network Traffic, as only the precise summary data gets transfered over the wires (between Database Server and Reporting Server),
2. Less Load on Database Server, as data gets processed one time that too during off-peak hours,
3. No Grouping and Summarizing of Data on the Reports' end, this make displaying of Report a breeze,
4. No need to store high volumes of data parsed from IIS Logs in database table, this further increases the database query processing speed,
I hope someone from Microsoft reads this post ;)
|