Some of the fields in these "records" can be ignored. Specifically, you may ignore the following pages (files) and fields:
Appendix B gives some hints about converting these files to other formats (such as RDBMS).
Finally, like most non-trivial, real-world situations, this dataset is incomplete and inconsistent. As you encounter problems, feel free to ask about them. You should think about what sort of inconsistencies might arise and how you will deal with them.
You can create an account in PostgreSQL via the PostgreSQL Help page mentioned earlier. You are free to create individual accounts, but in order to avoid having to grant access to others you may choose to share one account for the project.
A description of the deliverables follows:
Your report should contain an ER diagram of your final schema and PostgreSQL table definitions. You should discuss alternatives you considered and why you rejected them as well as how your design evolved over the course of the project
You should discuss the data loading process, what sort of things you had to consider or problems you encountered and how you dealt with them. In addition, you should also describe any optimizations you made to the database schema and justify your choices.
For each of the queries you should provide your translation into a single PostgreSQL SQL query along with a description of your approach. It may be the case that you could not translate all the queries to SQL due to the limitations of the language, limitations on PostgreSQL's implementation, or your database design. If you were unable to translate a query, you should explain why the query was not expressible. NOTE: I do not give brownie points for highly-convoluted non-general queries written to answer a particular question. Your queries should be short, elegant, and work for all cases. Do not attempt to "cook" the design of your database to answer a particularly difficult query.
The final report should also provide a short section summarizing your experience with the project (e.g., difficulties you experienced, lessons learned, novel solutions you employed, PostgreSQL experiences, and anything else you think interesting or notable). The final report should be relatively short, on the order of 6 - 10 pages, and not include code for populating the database nor database table listings.
Last modified: , by David M. Hansen