Course: Database Systems Discussion 1 (Chapter 3 – Course Textbook): Consider the ER diagram shown in Figure 3.22 for part of a BANK database (also below for reference). Each bank can have multiple
We can write your essays! Let our essay writing experts help you get that A in your next essay. Place your order today, and you will enjoy it. No plagiarism.
Order a Similar Paper Order a Different Paper
Course: Database Systems
Discussion 1 (Chapter 3 – Course Textbook):
Consider the ER diagram shown in Figure 3.22 for part of a BANK database (also below for reference). Each bank can have multiple branches, and each branch can have multiple accounts and loans.
(a) List the strong (nonweak) entity types in the ER diagram.
(b) Is there a weak entity type? If so, give its name, its partial key, and its identifying relationship.
(c) What constraints do the partial key and the identifying relationship of the weak entity type specify in this diagram?(
d) List the names of all relationship types, and specify the (min,max) constraint on each participation of an entity type in a relationship type. Justify your choices.
Figure 3.22 (please check this ER Diagram in attached document)
Discussion 2
Discussion 1 (Chapter 5): Discuss the characteristics of relations that make them different from ordinary tables and files.
Instructions:
Your response to the initial question should be 350 words. Next respond to two postings provided by your classmates. The first post should be made by Wednesday 11:59 p.m., EST. I am looking for active engagement in the discussion. Please engage early and often. You are require to create your initial thread in order to view and respond to the threads posted by other students. There must be at least one APA formatted reference (and APA in-text citation) to support the thoughts in the post as needed. Do not use direct quotes, rather rephrase the author’s words and continue to use in-text citations.
Course: Database Systems Discussion 1 (Chapter 3 – Course Textbook): Consider the ER diagram shown in Figure 3.22 for part of a BANK database (also below for reference). Each bank can have multiple
Course: Database Systems Discussion 1 (Chapter 3 – Course Textbook): Consider the ER diagram shown in Figure 3.22 for part of a BANK database (also below for reference). Each bank can have multiple
Reply to the below posts: Post 1: Michael Week 2 Discussion COLLAPSE Top of Form The strong entity types in the ER diagram are the BANK, ACCOUNT, LOAN, and CUSTOMER entities. The weak entity is the BANK_BRANCH. Its identifying relationship is the BRANCHES relationship, and the partial key is the branch_no. Since the branch_no is a partial key with an identifying relationship to BANK, it means that the branch_no may exist for multiple banks. To accurately identify which BANK_BRANCH, the branch_no, and code from BANK are required. There are four relationship types: ACCTS, LOANS, A_C, L_C, and BRANCHES. These are the relationships: A_C: M:N many-to-many L_C: M:N many-to-many ACCTS: 1:N one-to-many LOANS: 1:N one-to-many BRANCHES: 1:N one-to-many A bank can have multiple branches (1:N), and each branch can have multiple accounts and loans (1:N). Each account and loan can have many customers (M:N).Bottom of Form Post 2: 1 day ago Jerome Discussion 1 COLLAPSE Top of Form Consider the ER diagram shown in Figure 3.22 for part of a BANK database (also below for reference). Each bank can have multiple branches, and each branch can have multiple accounts and loans. A) List the strong (nonweak) entity types in the ER diagram. The strong entity types: BANK, ACCOUNT, LOAN, and CUSTOMER B) Is there a weak entity type? If so, give its name, its partial key, and its identifying relationship. The weak entity type: BANK_BRANCH Partial key: Branch_no Identifying relationship: BRANCHES C) What constraints do the partial key and the identifying relationship of the weak entity type specify in this diagram? Each branch has a unique branch number Each BANK_BRANCH will have exactly 1 BANK Each BANK will have 1 or more BANK_BRANCH D) List the names of all relationship types, and specify the (min,max) constraint on each participation of an entity type in a relationship type. Justify your choices. BRANCHES consists of BANK (1,N) and BANK_BRANCH (1,1) BANK and BANK_BRANCH have total participation Each bank must have one or more branches, and each branch must have exactly one bank ACCTS consists of BANK_BRANCH (0,N) and ACCOUNT (1,1) BANK_BRANCH has partial participation and ACCOUNT has total participation Each branch can have zero or more accounts, and each account must have exactly one branch A_C consists of ACCOUNT (1,N) and CUSTOMER (0,N) ACCOUNT has total participation and CUSTOMER has partial participation Each account must have one or more customers, and each customer can have zero or more accounts LOANS consists of BANK_BRANCH (0,N) and LOAN (1,1) BANK_BRANCH has partial participation and LOAN has total participation Each branch can have zero or more loans, and each loan must have exactly one branch L_C consists of LOAN (1,N) and CUSTOMER (0,N) LOAN has total participation and CUSTOMER has partial participation Each loan must have one or more customers, and each customer can have zero or more loans Bottom of Form
Course: Database Systems Discussion 1 (Chapter 3 – Course Textbook): Consider the ER diagram shown in Figure 3.22 for part of a BANK database (also below for reference). Each bank can have multiple
Replies to other posts: Post 1: 19 hours ago Naveen Kumar Discussion COLLAPSE Top of Form Ordinary tables and files are distinct. Apart from the laws of probability, they must be different with a unique source of information in their possession. They also have a particular purpose: to create a new model of reality, which in one sense is called knowledge or understanding. Some people, for instance, use the tables as a set of tools or, in the more modern terms, as a system of calculations, or they use the knowledge, or, in more familiar terms, a model of the world, as the primary form of logic, a tool of language, a tool of psychology. Nevertheless, what is more important, what makes them distinct from ordinary tables and files, which are just the basis of the table or file system, which in its current form is the same as this or that, which is to say merely the system of mathematics which in its simplest form, what goes into a table, is essentially the same as this, but which in its complex form, is the system of mathematics which goes into the mathematical table- The basic principle is in the tables (Su et al., 2020). They provide information about anything, about how it happened. They are the foundation of the world as it exists, of the table and the file, which the mathematical system, which in its simplest form, contains the whole of existence. Moreover, they are the basis for the world as it exists. In ordinary tables and files, each column in a file has nothing but its position; it is one place; there is no space between them. In the tables, however, it is possible to combine columns or rows and make other columns or rows; there is space between them; there are only a few columns and rows; the file is a whole; it is nothing less than the whole of a universe. The primitive data structures were designed to be used with data like ordinary tables and files. In these ways, they are not as general as an ordinary data structure, but they are still general enough to deal with much of the sort of stuff that ordinary data structures cannot do (Bhatta et al., 2020). References Bhatta, M., Gutierrez, L., Cammarota, L., Cardozo, F., Germán, S., Gómez-Guerrero, B., … & Castro, A. J. (2020). Multi-trait genomic prediction model increased the predictive ability for agronomic and malting quality traits in barley (Hordeum vulgare L.). G3: Genes, Genomes, Genetics, 10(3), 1113-1124. Su, L., Ma, X., Yu, H., Zhang, Z., Bian, P., Han, Y., … & Gai, Z. (2020). The different clinical characteristics of corona virus disease cases between children and their families in China–the character of children with COVID-19. Emerging microbes & infections, 9(1), 707-713 Bottom of Form Post 2: 16 hours ago Praneeth Praneeth – Week 2 Discussion 2 COLLAPSE Top of Form Relations can be told apart from files and tables in many ways. First, relations allow the users to do away with the content if it is not used by the user, which is not possible in files (Sciore, 2020). Updating of the information can also be done using relations as opposed to the files. Other than that, relations allow the users to save the needed databases, which is not possible in the tables and files. This is because the two are utilized locally. Another distinguishing factor is that the relations used database manager. This is contrary to files that make use of the file manager. Despite the two being useful, the database manager is better for firms that have long-term goals (Zhang & Ives, 2020). On data security matters, the information contained in the relations is more secure than the one contained in the files and tables. Following the increased information security cases as the years go by, relations are preferred by the major organization since they are assured of the status of their data. In some instances, information security can lead to irreversible losses in the firms; thus, being keen on the techniques used should be a factor that should be taken cautiously. In so doing, the investors will save the extra funds that could have been used unnecessarily. Based on all the mentioned factors above about relations, files, and tables, relations are better than the files and tables since, in most of the characteristics, the relations stand out. This makes relations more efficient than the two because most users consider efficiency in the modern information era (Sciore, 2020). Efficiency is a critical factor in the current business era where every venture tries to outfit others. The stakeholders should consider this aspect to ensure that the tools used match their expectations in the long run. References Sciore, E. (2020). Disk and File Management. In Database Design and Implementation (pp. 49-78). Springer, Cham. Retrieved fromhttps://link.springer.com/chapter/10.1007/978-3-030-33836-7_3 Zhang, Y., & Ives, Z. G. (2020, June). Finding related tables in data lakes for interactive data science. In Proceedings of the 2020 ACM SIGMOD International Conference on Management of Data (pp. 1951-1966). Retrieved from https://dl.acm.org/doi/abs/10.1145/3318464.3389726 Bottom of Form

Everyone needs a little help with academic work from time to time. Hire the best essay writing professionals working for us today!
Get a 15% discount for your first order
Order a Similar Paper Order a Different Paper