SUBJECT -INTRODUCTION TO DATABASE DESIGN- Please answer the following TWO questi
ID: 3766419 • Letter: S
Question
SUBJECT -INTRODUCTION TO DATABASE DESIGN-
Please answer the following TWO questions after reading CASE SCENARIO below questions. I am needing to write an essay, please explain your reasoning when answering questions.Thanks.
1. Develop a plan to meet the access requirements. Identify security principals involved for direct access to data and software requirements to facilitate connectivity. Compare and contrast how the data access design will vary depending on whether the database server supports a one-tier or two-tier security system.
2. Design a backup system that meets all of the specified requirements. Describe what backups will run, when, and to what destination(s). Compare design requirements when using permanent or removable storage media.
CASE SCENARIO- Planning a Secure Multitier Environment You are designing the database solution portion of a multitier application. The solution must support both direct client access through the local network and indirect access through an application server. There will be two management clients that need server access only. The application server requires encrypted communications with both the database server and its clients. You need to know who has been connected to the database server, and when, at any time.
Backups must be designed to minimize the amount of time required to back up data during the day for backups run between 7:00 a.m. and 6:00 p.m., when the last of these periodic backups are run. An additional backup should run each night at midnight and a full backup run each weekend. All backups must run without any operator interaction. The backup system must be set up so that no more than 30 minutes’ worth of work is at risk at any time and based around full, differential, and transaction log backups. Recovery should not require transaction log backups taken over multiple days. Backups should be immediately available for recovery.
Explanation / Answer
Here we are planning to
database server for a client/server database solution. The solution includes two production databases and one decision support database, all running on the same database server host. The data- bases will support multiple client applications, each running on the appropriate client machine, as well as direct access through scripts, procedures, and ad hoc queries run from command line interfaces. The database server and all clients are members of an Active Directory domain. Server and database access must be managed separately.
You must protect databases and the servers on which they reside; you must administer and protect the rights of internal database users; and you must guarantee the confidentiality of ecommerce customers as they access your database. With the Internet continually growing, the threat to data traveling over the network increases exponentially.
It is imperative that modern Web applications provide desktop-like rich browser interfaces using Asynchronous JavaScript and XML (Ajax) or the Google Web Toolkit (GWT) as well as RESTful Web services to external client applications. This article proposes a Resource Request Handler (RRH) for Ajax/GWT and calls from external client applications, and a Browser Request Handler (BRH) for processing requests from the browser and generating output to display in the browser. Both handlers share a common Business Logic Layer, which in turn interacts with the Data Access Layer. The extraction of RRH and BRH simplifies the design and helps facilitate code reuse, leading to a flexible and extensible architecture.
REST (REpresentation State Transfer) describes an architectural style of networked systems such as Web applications. It was first introduced in 2000 in a Ph.D dissertation by Roy Fielding, one of the principal authors of the HTTP specification. REST refers to a collection of architecture constraints and principles. An application or design, if it meets those constraints and principles, is RESTful.
One of the most important REST principles for Web applications is that the interaction between the client and server is stateless between requests. Each request from the client to the server must contain all of the information necessary to understand the request. The client wouldn't notice if the server were to be restarted at any point between the requests. Additionally, stateless requests are free to be answered by any available server, which is appropriate for an environment such as cloud computing. The client can cache the data to improve performance.
An operation window is a daily time period when a specific type of operation is allowed to occur. The main purpose of this feature is to help you prevent an unexpected, time-consuming operation from disrupting normal operations. Operation windows can be established either for the entire CommCell or for a specific iDataAgent. By default, all operations can be conducted at any time.
If a job is submitted outside of its window of operation, Galaxy puts the job into a pending status until the window of operation becomes valid. if you restrict backups to a 6:00 P.M. to 7:00 A.M. operation window, a backup that is scheduled for 1:00 P.M. remains pending until 6:00 P.M.
If a job is started within its window of operation, but does not complete before the operation window expires, Galaxy manages the job in one of the following ways:
Restartable jobs (it can be stopped and restarted at the point of suspension), are put into a pending status when the window expires, then restarted when the window of operation becomes valid again. In the preceding example, if a backup is still running when the 7:00 A.M. operation window expires, Galaxy suspends it until the next backup operation window begins at 6:00 P.M.
Non-restartable, are allowed to run to completion.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.