Month: June 2017

DAT601 Week 15, Day 1 – Final Class, Milestone Three Review

This was the final DAT601 class for the semester! Yay, we made it! 🙂

In this class, we reviewed the requirements for Milestone Three and briefly covered User Views

  • Users
  • Views
  • Roles
  • and Other Privileges

After this, we were to provide Todd with feedback on how he was, his teaching and the course this semester, unfortunately, however, I had to leave the class early so I missed this.

Users, Views, Roles and Other Privileges

All and all, these features are mostly security features. They allow you to restrict what a user can see in the database, this is helpful when you need different levels of access and data that varies in sensitivity, by allowing you to restrict low-level users to basic data and grant high-level users access to more sensitive data.

This control also allows us to simplify the users experience by removing redundant, or “back end” data, from their view, potentially such as ID’s or join information.

Feedback for Todd

As I was not in class for this section I thought it may be helpful to provide some feedback through the Journal.

Scope of the Course

I felt that the scope of the course was very good, it covered a lot of material and was certainly a large step up from the DAT501 course, presenting many new challenges, multiple new concepts and a MASSIVE hike in workload (my final report consists of almost 100 pages and over twenty-two and a half thousand words, not including the attached supporting files!), however, this is the level of work I had expected for a level 6 paper and overall I am satisfied with the content that was covered.

Todds Teaching Style

Unfortunately, I cannot give high praise to Todd’s teaching style, although I do sometimes find the odd lecture hard to follow when other tutors are presenting (this is usually a learning style preference opposed to a fault with the tutor’s presentation), I found Todd’s lectures increasingly harder to follow as the semester progressed.

I could put this down to many factors, however, if I had to make assumptions or a statement it would be that I increasingly felt that the lectures lacked preparation and were more conducted “on the fly” rather than with a solid plan for delivery, in some cases even having Todd getting confused along with the entire class and, once, having to re-do a lecture.

I found this unprofessional and a little bit disappointing, although, I do understand that there are potentially many other factors that could influence the way that the course was presented, such as illness or personal issues, I have to say that this had a huge impact on the confidence I feel on this subject and, coming towards the end of the semester, I’m still unsure if what I have learnt and understand is correct.

 

Advertisements

DAT601 Week 13, Day 2 – Transaction Analysis

In this class, we covered Transaction Analysis. The purpose of analysing transactions is to Understand the transactions or queries that will run on the database, including:

  • The Expected frequency of each transaction
  • Access to the relations and attributes along with the type of access such as:
    • Select, Insert, Update, Delete
  • The attributes used in the SQL
  • To check for pattern matching, range searches, or exact match key retrieve
  • Join attributes
  • Time constraints imposed on the transaction
  • Attributes (Columns) involved in any predicates for critical structures higher priority

Analysing transactions involves creating a transaction usage map and transaction tables

Tables look something like this:

Capture

And transaction maps can look something like this:

Capture2

DAT601 Week 13, Day 1 – Away, But not Missed

I was not present for this class, however, I ready over the Forum post that Todd put up and caught up with two of my classmates the next day and went over what was covered.

In this class we were to connect our SQL Server install to Todd’s server via an SSH tunnel, this was a breeze to complete after doing an exceptionally similar thing in DAT602, where we connected MySQL to the server.