Class 1 | Week 8 | DAT601

Today Todd is giving us talk that compared conceptual, logical and physical database designs and the differences between them, likely to properly define the differences between them before the class moves onto the next milestone of our project into the logical modeling phase.

He has also advised everyone in the class to install SQL server along with SQL management studio for our further physical designs, luckily I already have this software installed and I have simply verified that it is functioning correctly by creating a database within my local server.

Following this Todd his bought up the Milestone 3 brief to help explain what is required to us, his first point was that we are not locked into what we designed in the previous milestones, we can iterate upon what we did, we are to produce a report that integrates with our previous milestones into one master report.

Physical database design methodology appears to have many steps involved within it, it appears to be a complex process at first glance, I am slightly concerned with how much work this will involve going down the road but none the less it is still attainable.

Todd is providing us with a checklist for milestone three to guide us through the projects creation.

Todd has finished lecturing an hour in and is now helping people individually with their project.

Comments

Post a Comment

Popular posts from this blog

Class 2 | Week 9 | DAT601

Today's lesson pertains to more SQL language beginning with the GROUP by clauses, little examples are being shown on the projector for us, these kind of physical examples are a lot easier to digest than writing on the whiteboard. Group by must appear after the FROM and WHERE clauses, GROUP by groups rows into subgroups based on values of columns or expressions. Todd's example is used to group columns together to show a sum of total sales for a specific region. Another example of a group by rollup which is described as a niche function which caused some debate in class as to what it actually does. GROUP BY GROUPING SETS is used to allow multiple group-by clauses to operate in a single statement, GROUP BY GROUPING SETS is equivalent to the 'union' of two or more GROUP BY operation in the same result set. Next topic is Views within SQL, which is used to present the information data in a different point of view. This can simplify the access to specific information w...
Read more

Class 2 | Week 2 | DAT601

Image
Beginning this weeks second class Todd has provided an example document for our milestone one and is walking through it to help us understand the different types of tables he desires. Upon learning that this milestone is about 15 pages max I am feeling comfortable. After this he has continued with last weeks power point and explaining more conceptual database concepts in depth, including but not limited to: cardinality, weak vs strong entities, multiplicity constraints and so on. Below is some pictures from my teams brainstorming over our teams conceptual design done earlier today, nothing perfect but getting together to do this ignited some interesting conversation and I felt like we made progress in the end. Below are my class notes for today Cardinality     cardinality is the count of entities within the relationship Participation     specifies minimum number of relationship instances each entity can participate in     this is cal...
Read more

Class 1 | Week 14 | DAT601

Today's lesson pertained to an explanation of the Milestone three steps to get everyone on the same page before Todd started into a talk about database file structures and the different structures they may take. The following discussion resulted in a lot of in-depth information regarding storage sizes that is ideally relevant to the estimation of database storage size task we have to complete within milestone 3. The rest of the class has been assigned to milestone 3 work.
Read more