Featured Database Articles

We
will perform modifications to a copy of one of the existing Execution Log
reports we have uploaded, to customize it to meet a local requirement. The
procedure that we follow would be similar for modifications of any of the
sample reports, with obvious differences arising in varying layouts (use of a
table data region versus a matrix data region, etc.), and so forth. As we have
mentioned already, the reports provide an excellent starting point from which
to build a more "environment sensitive set," and we will pose a simple
scenario where this is just the action we take.

Let's
say that, upon review of the Execution Log reports we have uploaded, the
client information consumers group with whom we are working are excited with
the results we have been able to obtain so quickly. Almost immediately,
requests for modifications are communicated, but, then, that was just the
reaction we had hoped for. This sort of feedback will get us to the ultimate
report destination far faster than beginning with a blank drafting board, and
asking the group (a team with only minimal exposure to Reporting Services in
the first place) to describe "everything they wish to see in a performance
/ access report based upon the Execution Log."

One of
the first requests is for a modest set of changes to a report that has met with
immediate popularity: the Today's Reports report. The information
consumers tell us that, with the addition of 1) a report type (report,
snapshot, etc.) and 2) the physical location of the report (i.e., the
folder within which it is stored), Today's Reports will be perfect to
fit a current requirement. While more elaborate requests will no doubt follow,
we agree to make the changes once we confirm our understanding of them.