“Dimension relationship” refers to the direct or indirect relationships between dimension and its measure groups in a Cube.
||Refers to a standard relationship, when a Key column in the dimension is directly joined to fact table.
||When a Key column in the dimension is indirectly joined to fact table by referencing another dimension.
|Fact / Degenerate
||Dimensions constructed from attribute columns in fact tables than from attribute columns in dimension tables.
||One dimension is associated with multiple facts
Read more: https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models-olap-logical-cube-objects/dimension-relationships?view=sql-server-2017
Note: My study notes
Shu Ha Ri is a learning model, or technique where at first (Shu) he/she follows a master and does the activities without knowing the why factor. He follows only one way of doing an activity even though there are different and efficient ways to accomplish same. Later (Ha) he learns more about the underlying details and starts to learn from different sources or masters and starts to do activities more efficiently. At the final stage (Ri) he starts to think of their own and builds his on ways of doing things within his comfort zone.
– Used for the storage of noncritical items but which requires fast read-write.
– Does not have parity (parity is about checking whether the data has been lost or overwritten on transition)
– Does not have redundancy or fault tolerance. i.e., when the drive dies, the data is lost.
– Used usually for OS, SQL Engine etc. installation
– Two or more disks used to write data and is in parallel
– High performance
– High availability
– No data loss on disk failure
- RAID 2
- RAID 3
- RAID 4
- RAID 5 – Striping with Parity
Requires 3-16 drives
No data loss on disk failure
Read is faster but write can be slower
Failures can impact throughput
- RAID 6 – Striping with Double Parity
Requires min. 4 drives.
Two drives are used for storing parity data
Read is faster but write can be slower than RAID 5
More secure than RAID 5
- RAID 7
- RAID 10 / RAID 1+0 – Striped Set of Mirrors
10 means combining 1 and 0, and not “ten”
Combines disk mirroring and disk striping
Requires minimum 4 disks
Best choice for I/O intensive applications
Note: Blog incomplete. Will be updated.
Note: My learning notes, source: Internet
Write a program in a computer language of your choice to convert any given text to “leet format” in real time.
Leet (or “1337”), is a system of modified spellings used primarily on the Internet.
Input: “Translator” Output:”Tr4nsl4t0r”
Input: “leet”, Output: “l33t”
Input: “Good Morning”, Output: “G00d M0rn1ng”
- Code Quality Standards
- OOAD/Object-Oriented Analysis & Design
- Application Logic
- Exception Handling
- Simplicity and Effectiveness of code
Time: 0-30 minutes max.
Write a program in a language of your choice to find the critical path from a given set of tasks.
A critical path is determined by identifying the longest stretch of dependent activities and measuring the time required to complete them from start to finish.
Each circle (A-G) are tasks with specific duration (in Hours).
Array of task names and duration given in the diagram.
1. Longest path (Critical path) is A+G+B+F+C+D (42Hrs)
2. Shortest path is A+B+C+D (26 Hrs)
Registration & Agenda here.
Well, the question is slightly wrong until the context is specified because it is possible to build Modern Data Warehouse by including Cosmos DB in the architecture. This is too much relevant today because the data is no more straight forward content with human readable entities and relations (structured), but unstructured and/or streaming too. Also the pace of the data flow, or business requirement is becoming near real-time.
See a reference architecture below:
Image Source: MS Docs
Here, in this blog, the context is about Traditional Data Warehouse possibility, where you will be modelling the data, specifying relationships, etc. Let us look at the definition of Data Warehouse mentioned in Oracle Docs:
“A data warehouse is a relational database that is designed for query and analysis rather than for transaction processing.”
Now let us ask the right question – Why Cosmos DB may not be apt for using as a data store in a Data Warehouse? – It is not apt, because, Cosmos DB is a NoSQL database where it is literally not easy to draw relationships between entities/tables/data. Check what MSDN blog said about this:
“Cosmos DB is not a relational database. You cannot just take your relational database and expect it to run in Cosmos DB. You could move tables of data into Cosmos, but not the relational aspects of your existing data structures.”
As of today, this is the conclusion. But we cannot say tomorrow what will happen to these concepts because Cosmos DB is becoming powerful and I am already in love with it.
You can read common scenarios (use cases) where you can use, or the companies use Cosmos DB here.
Do you have different thoughts on this? Please comment.
Walk In to Orion Hyderabad office on 17th November 2018.
Blockchain is the next big thing in this… oops, I mean the current BIG thing in the industry. Want to know more about what is Blockchain, how is it implemented and, would you love to hear about the experiences of professionals already in Blockchain space? Come to Orion Business Innovation, Kochi Infopark this Saturday, 10th November 2018 at 3:00PM and let us have a Coffee. You can show your interest directly in this meetup page.
We will be planning for a series of sessions on Blockchain so do not left behind.