1 week project at SeFocus where students were provided a working database and were then requred to create stored procedures which would drive Reporting Services Reports.
MongoDB .local Munich 2019: A Complete Methodology to Data Modeling for MongoDB
SetFocus Reporting Services Project
1. Reporting Services Project
Duration: 1 week
Program: SetFocus SQL Server 2005 Masters Program
The SetFocus Library has a database created on SQL Server 2005 called
Library. The administrators of the library need you to create several reports using
Microsoft SQL Server Reporting Services to accommodate their business
practices. Please take their requests into consideration and submit these in a
professional, dignified yet stylish format as you would on a future contract
assignment. You have been allotted one week to complete all project
requirements.
They require the following reports:
1. rpt1ListOfBooks - List of books currently held by the library (by ISBN). It
should contain a drill-down that provides detailed summary information
about the book.
2. rpt2NumberOfCopies - Number of copies per title.List the books by rows
and languages by column in a matrix format as shown in the table below:
Chinese English
The Cherry Tree 20 20
Frankenstein 20 20
3. rpt3MostActiveMembers - Most active members (# of loans per member)
with an option by month, and also by calendar year. You can use just the
loanhist table for this report, however if you include current loans, 1 point
EC will be granted.
4. rpt4BooksCheckedOut - List of books currently checked out. Order by
ISBN, Copy Number (include member name)
5. rpt5AdultMemberDetails - Details about adult members: name, address,
total number of active checkouts (loan table), with a subsequent option for
total fines assessed, total fines paid, total fines waived, and total due (for
now- use loanhist only for this fine information), and a hyperlink (drill
through) to a second report showing any dependants and that displays
checkout/fine information- (address information here is not necessary as it
will be the same as the sponsoring adult in the Library database).
2. 6. rpt6ListOfChildrenTurning18 -List of Children who have turned 18 within
the last six months, and those that will turn 18 in the next six months.
Please distinguish between the two groups by utilizing a color scheme,
and be sure to explain this scheme to the user in a legend.
7. rpt7ExpiredMemberships -A complete list of expired memberships,
organized by adults and all dependant memberships.
8. rpt8ReferenceAndCollectionItems - The Library would like a list of
Reference and Special Collection items (Stored in the database as
loanable = N). Include ISBN and Copy Number. Feel free to change some
of the entries in the item table as appropriate to test this report.
9. rpt9OverdueBooks - A report for all overdue books, member name, and
current fines due against books that have not been checked in (use the
Loan table – don’t worry about fine information in the Loan History table)
Calculate these fines as 25 cents per day. (2 points E.C.: you can design
a report that will be ordered by member name that will also accommodate
the fine information in the Loan History table- something you already have
available in another report).
To avoid schema conflicts, no database schema changes will be allowed
(Implement DDL Triggers)
Please also propose a Backup and Maintenance plan for the Library. Include
rationale for your proposal (screenshots are also helpful).
Hints and Gradepoints:
• Make sure 'Data Source=.' in all report
• 1 point per report will be purely related to aesthetic and intuitive design:
i.e. use of design, colors, headers, etc.
• Report Order should be submitted in the same order as listed above.
• Report Headers and Footers should be consistent in line with the design
of the report (Be sure your design carries past the first page).
• If you are stuck, realize one point is all design – so do that first. Another
way would be to focus on the queries first.
3. Project: Reporting Project Grade Sheet - SetFocus SQL Server 2005 Masters Program
Date corrected: August 5, 2009
Student: (/37) %
Reports/Triggers/BackupPlan – /32 Comments:
Report 1
Report 2
Report 3
Report 4
Report 5
Report 6
Report 7
Report 8
Report 9
DDL Triggers
Backup Plan – organized, thoughtful presentation.
Code(Look/Appeal) – 2 Comments:
Project is submitted in proper format, compiles, and runs, and
code is easy to follow; i.e. “readable”
Documentation -- 3 Comments:
.
Well planned approach to meeting the requirements
Worked independently and effectively
PERCENTAGE /100 % /37