When Microsoft announced in 2003 that it was going to release SQL Server Reporting Services (SRS) as a SQL Server 2000 add-on, there was a frenzy of excitement. The product was originally slated for release with SQL Server 2005, formerly codenamed “Yukon,” so the early release was a welcome event for many. Our software development company decided to embrace SRS early on, and was fortunate to work with Microsoft during the beta phases. In January 2004, the month SRS went RTM (Released To Manufacturing), we deployed it immediately. We intended to migrate all our existing reports, which had been developed in as many as five reporting applications and platforms over the past ten years. We can sum up the reason for the seemingly rapid decision in one word: standardization. We needed to provide a standard reporting solution to our customers, just as Microsoft wanted to create an industry standard with the Report Definition Language (RDL), which is the Extensible Markup Language (XML) schema that dictates the common structure of all SRS reports. Even in a version 1 product, SRS delivered almost all the features that we needed from day one. Thanks to its extensibility, we could programmati-cally add other features that weren’t directly supported in version 1. In addition, Microsoft has committed to enhancing SRS over time. For example, Service Pack 1 of SRS is out, and SQL Server 2005 will include a number of SRS enhancements.
KeywordsFile Share Report Manager Management Request Software Development Company High Priarities
Unable to display preview. Download preview PDF.