I’ve provided 2 discussions that need to be responded separately.
1-)My group’s project deals with the delivery of medication at a hospital. Add is needed to allow new medications, employees, locations, and patients. Delete will be used to remove employees who are no longer with the hospital. Also, will be used to remove medications that are not being used anymore. For patients would who move to different parts of the hospital, their location will need to be updated. Update will ensure that accurate information could be made available after changes have occurred.
For backup I would have a Full and a Differential. Because of the characteristics of a hospital, I do not perceive there is ever really a downtime. If there is, I do not imagine that there is a time when the facility could afford to not have access to a database. The hospital should have at least two databases running interchangeably. With that set up while one is being backed up the other database is available to function. The roles would change throughout the day. Backups should be done every four hours. It would decrease the amount of time it takes to backup the data.
2-)In our database, the transactions in our patient table can be added, updated, and deleted. For example, every time a patient is admitted to the hospital multiple rows in tables will be updated. Admission date and time, medications, nursing unit location, employee, and delivery time and date will all be updated. The users authorized for updating patient information will consist of doctors, nurses, pharmacy, and human resources staff members. To tune the performance of the database in the DBMS, we would use backup and recovery health checks.
The main purpose of a backup is as a safeguard against unexpected data loss and application errors. Backups will be completed daily (around 2 am) as updates, insertions/additions and deletions of rows changes in tables. Our recovery plan will include a list of all group members along with their contact information, roles, and responsibilities.
The recovery of individual transactions focuses on specific individual transactions, a series of actions, carried out by a single user or an application program, which reads or updates the contents of a database. However, the main focus of the recovery of an entire database is to undo or restart any transaction that was running at the time of failure and redo any transactions that committed since the last checkpoint.