By Garth Jones

I review a lot of SQL Server Reporting Services (SSRS) reports and one of the most common problems I encounter is page sizing.

Most people design reports to look very nice in interactive mode, but they forget that these reports are often printed or exported to other file formats.

The last thing you need is someone complaining about not being able to follow your report.

Here’s an example of what I mean below. Notice in the first screenshot that the Detail Devices section overlaps the page and the remainder of this section appears in the second screenshot?

Also, see how there is a blank area next the Service Pack Version column? In the interactive mode this would be the start of the Model column which you see in the following screenshot.

The Model column is pushed to the second page, so that it doesn’t get cut off midway. As a result, this column is shifted to the right and the Console ID column ends up being partly in the Patch Details section.

To solve this type of problem, I suggest using landscape orientation, a 14” x 8.5” page size, and reducing the number of columns to fit the page.

Importance of Page Sizing - Screenshot 1

Importance of Page Sizing - Screenshot 2