17.06.2013 Views

Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 17: Reporting for Duty, Sir! A Look At Reporting Services<br />

530<br />

Note that other than some messages that flash by while the report is generating, there will be very little to<br />

see in this dialog unless something has gone wrong (in which case, you’ll see related messages reflected in<br />

the dialog). Click Finish, and we can begin to see the results of what we just created, which should look<br />

something like Figure 17-18.<br />

Figure 17-18<br />

Be sure to take the time to explore the Report Model. <strong>SQL</strong> <strong>Server</strong> will make assumptions about what you<br />

do and do not want to have shown, and it will not always make the right choice for your particular database<br />

usage. Look at what it has included, what it has added, and what it has generated in the way of<br />

derived attributes (rollups and such).<br />

Let’s take a quick look at an example of a value that will default to hidden when the wizard is done<br />

building the model, but that is sometimes useful in our reports. Start by navigating to the SalesOrder-<br />

Header table. Notice how the Sales Order ID column is grayed out. If you click on it and check the<br />

property window shown in Figure 17-19, you should notice that this possibly important field has been<br />

defined as being hidden.<br />

Figure 17-19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!