SQL Server
51 out of 78 rated this helpful - Rate this topic

SQL Server Reporting Services

Microsoft SQL Server 2005 Reporting Services (SSRS) delivers enterprise, Web-enabled reporting functionality so you can create reports that draw content from a variety of data sources, publish reports in various formats, and centrally manage security and subscriptions. For information about other SQL Server 2005 components, tools, and resources, see SQL Server 2005 Books Online.

The following InfoCenters organize the topics in SQL Server Books Online into content areas that are useful for specific roles. You can use the InfoCenters to find topics that provide you with the most relevant information for your job. In addition to InfoCenter pages, each topic in Books Online indicates the intended audience so that you can tell at a glance whether the topic contains content of interest to you.

Information worker icon Reporting Services Information Worker InfoCenter Provides links to fundamental information for creating, publishing, and accessing reports in Reporting Services.
Analyst role icon Reporting Services Analyst InfoCenter Provides links for data analysts who need to design, query, and manipulate data and report models using Reporting Services.
Administrator icon Reporting Services Administrator InfoCenter Provides links to relevant topics for installing and administering Reporting Services.
Developer icon Reporting Services Developer InfoCenter Provides links to the technologies and languages available to implement Reporting Services solutions programmatically.
Reporting Services icon Reporting Services Documentation Map Provides an overview of SQL Server Reporting Services, with links to all the major documentation sections in Books Online.

Components that interface with Reporting Services

Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
A total waste of developers time and energy...another Microsoft failure!!!!
What a piece of ***!!!! Don't go this route if you want reports that are easy to develop. You get extra pages and absolutely NO indication from the tool as to why. There is NOTHING overlapping the printable area, ( but you have to guess what that area is) and you STILL get an extra page with NO Data. What a phenominal waste of developers time trying to figure out WHERE and WHAT causes the second "mysterious" page. Stay away from this product or you'll be sorry!

Edit by another user:

Take a look at page size and margins. Then look at the body size, this might be where the problem lies. Page size minus margins must be equal to or larger than the body size, otherwise you get extra blank pages. Also, be sure to move the report body (on the right) back to touch the contents to make the page as small as possible.

Edit by yet another user:
As with any development tool, it pays to learn how to use it. In this case, a short read of report rendering and pagination MSDN articles would have solved the frustration.
If you're a developer that has no issue learning - go ahead and use RS, it's a great tool, best on the market by far.

If you're a developer who has a problem referring to documentation, it might be best to stay away from RS, and any other development tool.
This is a great product!!
My company has had great success using SQL Server Reporting Services and Report Builder 2.0. It does require developer skills to implement and use intially, but any decent report developer with experience in Excel and Access can use it just fine. MS provides excellent tutorials and documentation at all levels for this product.

This product is especially awesome if you integrate it with Sharepoint. For a basically free tool, this is a wonderful product. Developing reports is not hard with this product - if you know SQL and read the Help provided by MS.

As for the second "mysterious" page portlandpete complains about - set the Report property ConsumeContainerWhitespace to true and adjust your margins! I easily found this information with a basic Internet search.

Why do people think that new MS products are supposed to be easy to use by developers that can't be bothered to read the documentation or the tutorials?
Easy answer
It's your margins.