Types Of Actions Involve Databases
Sep 22,21Types Of Actions Involve Databases
Question:
1. What four main types of actions involve databases? Briefly discuss each.?
2. What are the responsibilities of the DBA and the database designers?
3. What is the difference between a database schema and a database state?
4. What is the difference between procedural and nonprocedural DMLs?
5. What is the difference between the two-tier and three-tier client/server architectures?
Answer:
Introduction
1. What four main types of actions involve databases? Briefly discuss each?
The four key types in the actions concerning the databases shall include the following: [1] Define Database, [2] Construct Database, [3] Manipulate Database, and [4] Share database (Hoffer et al., 2016). Firstly, for defining the database, it shall be required in defining the database akin to database structure as well as database type, and the same is referred as a metadata concerning the specific data. Secondly, it shall be required in construct database, which represents a process, for data to get stored as well as the same could be suitably maintained using the relevant Database Management Systems (“DBMS”) (Hoffer et al., 2016). DBMS refers to the software which aids in storing as well as retrieving of the data pertaining to users whilst also considering suitable set of security measures. The same shall comprise of the group encompassing programs that shall undertake manipulation of the database. In effect, DBMS shall accept requests pertaining to data by way of application as well as makes instruction for operating system with an aim of providing specific set of data. In case of larger systems, the DBMS shall aid the users as well as other form of third-party software for storing as well as retrieving data. In effect, DBMS shall allow the users for creating their respective set of databases aligned to the pertinent requirements.
This term of DBMS encompasses the users pertaining to database as well as other various application programs. The same offers the specific interface in-between data as well as software applications. Then, the case of Manipulate Database, wherein it shall entail the retrieving database in the manner of using query as well as insert, updating and also deleting database as well. Lastly, Share Database shall entail actions wherein the actions involve the sharing of information such that data shall get utilised amongst the varied users (Hoffer et al., 2016).
2. What are the responsibilities of the DBA and the database designers?
DBA as well as database designers shall both be responsible for undertaking data maintenance as well as data construction concerning the relevant organisation (Hoffer et al., 2016). The key set of responsibilities with respect to DBA as well as database designer shall include the following: [1] database security, [2] design database, [3] implementation of the data models, [4] resolving the capacity issues, [5] resolving the performance issues, and [6] maintaining the database (Hoffer et al., 2016).
3. What is the difference between a database schema and a database state?
In effect, database schema shall refer to the metadata (Gorman, 2014). It shall represent the initial level of stage with respect to the concerned database. While the database shall be defined as well as implemented in the initial time, database schema alone shall be defined with respect to this instance (Gorman, 2014).
In essence, database state shall refer to a state entailing the database and the same shall get changed in each of the action up till this database. Later, when database shall get implemented during the initial time, state of the database shall be null and post the insertion of data as database, concerned databases shall get suitably changed (Gorman, 2014).
In effect, database schema shall be referred as an intension whilst the state of database shall be referred as that of extension within the specific database (Gorman, 2014).
4. What is the difference between procedural and nonprocedural DMLs?
DML stands for data manipulation language, and the operations of data manipulation shall be described as follows: [1] insertion within the database, [2] retrieval of the database, [3] editing the database, and [4] deleting of database (Elmasri & Navathe, 2017).
The language of data manipulation shall represent a highly critical element within the overall context of DBMS (Elmasri & Navathe, 2017). The same shall essentially be supported using all elements of DBMS. Om this case, there can noted to be two forms in the languages of data manipulation, that is, [1] Procedural form of Data Manipulation Language, and [2] Non-procedural form of Data Manipulation Language (Elmasri & Navathe, 2017). Database shall get implemented during the initial time, state of the database shall be null and post the insertion of data as database, concerned databases shall get suitably changed
Procedural form of Data Manipulation Language:
Procedural form of Data Manipulation Language refers to a language that shall define on which of the data needs shall be required for being retrieve on as well as define overall process in addition. Once the data has been retrieved, the other forms of data could suitably be retrieved using same form of procedure (Elmasri & Navathe, 2017).
Non-procedural form of Data Manipulation Language:
Non-procedural form of Data Manipulation Language refers to a language that shall define what data shall be required in being retrieved by not specifying the specific process (Elmasri & Navathe, 2017).
5. What is the difference between the two-tier and three-tier client/server architectures?
There can noted to be two forms in the architecture of client server, that is, [1] two-tier form of architecture, and [2] three-tier form of architecture (Elmasri & Navathe, 2017).
Two-tier architecture:
The same represents a fundamental type with respect to the architecture of client server. Herein, the two-tier form of architecture shall in general be used across all of the communication networks (Elmasri & Navathe, 2017).
In the said context, concerned client shall send in the requests towards the relevant server with respect to the required resources as well as the server shall respond in a direct manner towards the concerned client. Herein, there shall be none of the third party who shall be involved within the overall process. This server shall not call other set of applications or else any forms in the machine for accomplishing the request of the users (Elmasri & Navathe, 2017).
Three-tier architecture:
In the architecture of this nature, there shall be sole middle layer which shall exist in-between user as well as that of database systems. Further, middle layer shall refer to application server which shall then interact amongst the client as well as data server (Elmasri & Navathe, 2017).
In this context, three shall be critical units with respect to three-tier architecture as follows, (1) Client: the requests by the client with respect to resources for the server as well as being equipped by way of user interfaces concerning the relevant presentation pertaining to responses concerning the server (Elmasri & Navathe, 2017), (2) Application Server: This application server shall represent a middle layer within three-tier form of architecture concerning the client server. Herein, application server shall offer critical set of resources towards th concerned clients who shall then be requested from the standpoint of the client with respect to user interfaces. This application server shall call other database servers for completing the task specified as planned (Elmasri & Navathe, 2017), and (3) Data Server: Herein, data server shall represent critical form of unit with respect to the three-tier architecture concerning. This data server shall offer the data towards the concerned application server which shall be required (Elmasri & Navathe, 2017).
References
Elmasri, R., & Navathe, S. (2017). Fundamentals of database systems (Vol. 7). Pearson.
Gorman, M. M. (2014). Database management systems: understanding and applying database technology. Butterworth-Heinemann.
Hoffer, J., Venkataraman, R., & Topi, H. (2016). Modern database management. Pearson Education Limited.