Prompt SnubHub! is the latest place to purchase tickets to…PromptSnubHub! is the latest place to purchase tickets to exclusive events other people get routinely turned down to.Part of its database consists of tables with information about Snubbies, as SnubHub! users are known, as well as for events, the venues for these events, and ticket listings and sales. The tables which form part of the SnubHub database are Users, TicketSales, TicketListings, Events, and Venues.Membership is by invitation only, and people routinely get turned down. Once accepted, users provide their last and first names, along with a valid email address. Thus, the database contains last names (limited to 20 characters and stored as UserLastName), first names (UserFirstName, 15 characters), and email addresses (UserEmailAddress, 25 characters). A system-generated user ID (UserID) is assigned to all users.Ticket listings (tickets offered for sale by Snubbies) are tracked using a system-generated ID assigned to any group of tickets being listed (TicketListingID). The listing includes the number of tickets being sold (NumTickets), the price per ticket (PricePerTicket), and a system-generated event ID (EventID). Sellers are identified by a field called SellerID which uses UserID numbers to uniquely identify each one. This is done in order to be able to obtain useful information separately about Snubbies when acting as buyers or as sellers.Ticket sales are assigned a system-generated ID per sale or transaction (TransactionID), tying it to buyers (BuyerID, same as UserID), and identifying the ticket listing purchased.Venues and events are tracked using the name (VenueName, 25 chars), city (VenueCity, 25 chars), and state (VenueState, 2 chars) of the venue hosting the event, as well as the name of the event (EventName, 50 char), and its date (EventDate) and time (EventTime).Both venues and events are assigned unique system-generated ID numbers (VenueID, EventID) to help track sales. As part of the Database Administration team, your job is to:1. Make a single listing all attributes/fields above, and any other fields necessary for implementation (if any)2. Identify all functional dependencies3. Normalize database to 3NF4. Think about and determine what all the appropriate attributes/fields/columns/legal values required in these tables should be to adequately support the scenario described above, prior to any coding5. Implement the database using MS Access or Oracle 19c software (whatever you have up and running) subject to the following conditions:o TablesmustbefullycreatedusingseparateSQLstatements(tablename,fieldnames,data types, field size, primary and foreign keys, etc.).o Each SQL statement must be saved as a separate query named Table_NameTable, e.g., UsersTable, TicketSalesTable, etc. Careful attention must be paid to spelling.o When used as foreign keys, each field name is modified by adding “_FK” to it to differentiate it from the field in the parent table. For example, if the field Field1 is used as a foreign key, it is called Field1_FK in the child table.6. Make a ERD (Entity Relationship Diagram) Deliverables DB Constructiono All fields are named correctlyo All fields are specified correctlyo All Primary keys defined correctly in all tables o All Foreign keys defined correctly in all tables o All queries saved and labeled correctlyo All table-creating queries executed correctly Diagramo All fields in all tables are unobstructedo All relations between all tables are unobstructed Databaseo A single data base file(a screenshot works) Additional Information The SQL statement needed to create primary keys has the following format: o FieldNameDataTypeSizePRIMARYKEYoro FieldNameDataTypeSize,PRIMARY KEY (FieldName)A system-generated primary key is created with the following statement o FieldNameAutoIncrementPRIMARYKEYNote: Size is no longer needed because the size of the field is managed automatically by the systemoro FieldNameAutoIncrement,PRIMARY KEY (FieldName)The SQL statement needed to create foreign keys has one of the following two formats:o FOREIGNKEY(ForeignKeyFieldName)REFERENCESReferenceTable(FieldName) oro ForeignKeyFieldNameDataTypeREFERENCESReferenceTable(FieldName) Computer ScienceEngineering & TechnologyMYSQLINF 218
Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.
You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.Read more
Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.Read more
Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.Read more
Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.Read more
By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.Read more