Schema

We have used snow-flake schema for storing the transactional data. In Fig the used schema diagram with the hierarchies are given, where we have shown the ERD of the schema. Here we have shown the hierarchy and the fact table. This is a sort of snowflake schema, and in the ERD there is two reference of BranchInfo related to the transaction table. They can be described as one is for where the transaction executed, and other branch reference through AccountInfo is for account to which the balance is changed. Thus they may not same. Hence this information is not redundant. And we get bank information from the account information. For inter bank transaction or inter account transaction here will be two entries in the fact table, one for debit and other for credit. In the diagram we see that there is a range hierarchy. Range is a concrete attribute but in the schema we made it discrete attribute to ensure faster query response. Query with a concrete attribute require more time than the query with discrete attribute. So, we transfer the concrete attribute into discrete attribute. Similarly we made the time hierarchy, and the last type hierarchy is for transaction type. This will define what type of transaction is defined by the entry.

All these are based on banking system. A data warehouse for banking system.