Petcare Vet Clinic needs to normalise records of appointments. An owner brings their pet to the appointment at a specified date/time with a specific vet. PetType means cat, dog, guinea pig, etc. Booking channel name can be phone, website, Facebook message, email. Below is the Appointment relation Appointment (vetID, vetName (PetID, PetName, PetType, OwnerMobile, OwnerFullName, channelID, channelName, date, time)) Convert the non-normalised relation to 1NF. Identify PKs using underlining, FKs using italics, PFK - underlining+italics. You may not introduce surrogate keys.

You own a pet care center. What fields might you enter when you create a table for dogs that you care for?Check All That ApplyOwner's last nameOwner's last namePet's namePet's nameOwner's driver license numberOwner's driver license numberOwner's addressOwner's address

In a veterinary office. the owner of the pet(s) is referred to as:Athe parentBthe clientCadministratorDsole proprietor

In a veterinary office. the owner of the pet(s) is referred to as:AadministratorBthe parentCthe clientDsole proprietor

Give the definition of four classes, Person, Doctor, Patient and Billing, whose objects are records for a clinic. Class Doctor will be derived from the class Person. A doctor have it’s specialty and  feesPatient will be derived from the class Person. A Patient record no_of_days_admitted and a Doctor object.A Billing object will contain a Patient object, Be sure your classes have a reasonable complement of constructors.First write a driver program to test all your member functions, and  creates at least two patients, at least two doctors, and at least two Billing recordsAt the time of Billing the Patient’s Doctor  name and Billing object’s doctor name equality should be checked.Total bill generated will be no of days the patient admitted * doctor's fees.

Mia is developing a health monitoring app to track user activities and vital signs. The app needs to handle three main types of data: OWNERS, PROPERTIES, and TENANTSWrite the DDL statements to create the following tables with the mentioned constraints to handle the data: The OWNERS table has a named primary key constraint pk_owners for OwnerID.The PROPERTIES table has a named primary key constraint pk_properties for VehicleID and a named foreign key constraint fk_owner that references OwnerID in OWNERS table.The TENANTS table has a named primary key constraint pk_tenants forTenantID.symbol refers to the primary key NN refers to Not NULLWhile creating a table PROPERTIES include a foreign key named fk_owner for the column OwnerID with the references of OWNERS table (OwnerID)After creating the tables, Mia needs to:Add the foreign key fk_property_id to the TENANTS table with the references of the PROPERTIES table(propertyID).Drop the foreign key fk_owner from the PROPERTIES table as it is no longer required.Note: The user must write only the query to create and alter the table. The query to display the description of the table is already given.Input format :No console inputOutput format :The output displays the successful table creation status and the structure of all three tablesRefer to the sample output.Sample test cases :Input 1 :Output 1 :Table OWNERS created.Table PROPERTIES created.Table TENANTS created.Table TENANTS altered.Table PROPERTIES altered. Name Null? Type ______________ ___________ ________________ OWNERID NOT NULL NUMBER NAME VARCHAR2(100) CONTACTINFO VARCHAR2(100) Name Null? Type _____________ ___________ ________________ PROPERTYID NOT NULL NUMBER OWNERID NOT NULL NUMBER ADDRESS VARCHAR2(255) Name Null? Type _____________ ___________ ________________ TENANTID NOT NULL NUMBER PROPERTYID NOT NULL NUMBER TENANTNAME VARCHAR2(100) TABLE_NAME COLUMN_NAME POSITION STATUS _____________ ______________ ___________ __________ OWNERS OWNERID 1 ENABLED 1 row selected.