I want to create logical database design: 1. Normalize the relations to at least third normal form (3NF) using proper standard E-R diagram notation. Provide the appropriate relational schema reduction. 2. Identify the primary and foreign keys for each relation (using appropriate notation). Maybe either list the primary and foreign keys or generate a schema diagram??? 3. Identify and describe any indexes needed to speed up searches on non-key attributes – can you explain it too? So I would understand why you come up with the answer please? 4. Identify and describe unique, conditional (check), non-null, referential integrity, or other constraints needed to guarantee the integrity of the database.5. Describe the set of business or workflow rules applicable to your project. Next, describe at what point in the workflow you will implement the business or workflow logic and the justification for doing so.Below are my conceptual design. Domain of the Problem:In this project, the domain revolves around managing various aspects of a Discord community focused onartistic activities and engagement. The Discord server hosts events such as drawing sessions, dailyquestions, surprise prompts, monthly prompts, and other ongoing activities. The goal is to create adatabase system that keeps track of key information related to these events, such as moderatorsresponsible for a given week, questions of the day (QOTD), prompts for different events, their usagehistory, member participation, and response ratings. This databae aims to provide efficient eventmanagement and historical tracking to enhance community engagement and content planning.Questions to Ask the Client:1. Event Details:What are the key events held in the Discord community, and how often do they occur?Are there specific moderators assigned to each event, and how is this responsibilityscheduled?Conceptual data modeling2. Questions of the Day (QOTD):How are the QOTDs generated, and who is responsible for them?How is the response rating (1-10) determined, and how often is it recorded?Can a QOTD belong to multiple categories (e.g., scary, fun, serious)?3. Prompts:How are prompts created and scheduled for surprise, monthly, and ongoing events?Are prompts reused, and if so, how often?What data do you want to collect about member participation in these events?4. Archives:What criteria determine when an event is moved to the archives, and what data should beretained for archived events?5. User interface website:What would be the efficient website design for the best use? E-R Diagram and Schema Diagram:ModeratorModerator IDNameDiscord UsernameScheduleResposibleo.nResposible on-Surprise PromptPromptIDPromptUsedDate Started#ParticipantsSurprise PromptPromptID intstrPromptUsedintDate Startedstr#Participants intPromptPromptID intDate IDintpromptstrQOTDIDQuestionAskedDate AskedRespond RatingCategoriesQOTDMonthly PromptPromptIDPromptUsedDate Started#ParticipantsQOTDQOTDIDQuestionAskedDate AskedRespond RatingCategoriesMonthly PromptPromptID intPromptstrUsedDate Started#ParticipantsintstrintintstrintstrintstrDateDate IDDateEventEvent IDEvent IDPromptUsedDate Started#ParticipantsOngoing EventOngoing EventintEventEvent IDEvent NameDate IDPrompt IDPromptUsedDate Startedstr#Participants intintStrstrintParticipent (member)StrintintArchivesEvent IDPromptUsedDate Started#ParticipantsEvent IDPromptUsedModeratorModerator IDNameDiscord UsernameScheduleArchivesDate Started#Participantsintstrintstrintintstrstrstr

Que) Normalize the relations to at least the third normal form (3 NF) using proper standard E-R diagram notation. Provides the appropriate relational schema reduction. Solution: Normalize the relations to at least the third normal form (3 NF) using standard E-R diagram notation. Provides the appropriate relational schema reduction.The process of normalization is about reducing data redundancy and ensuring data integrity by organizing data into separate tables. Here's the normalized structure for your project:Tables:ModeratorModerator ID (Primary Key)NameDiscord UsernameScheduleSurprise Prompt Prompt ID(Primary Key)PromptDate StartedParticipantsModeratorID (Foreign Key)Monthly Prompt Prompt ID(Primary Key)PromptDate StartedParticipantsEvent ID (Foreign Key)Ongoing Event Event ID(Primary Key)PromptDate StartedParticipantsEvento ID (Foreign Key)ArchivesEvent ID (Primary Key)PromptDate StartedParticipantsEvento ID (Foreign Key)QOTDQOTDID (Primary Key)Responsible (Foreign Key)QuestionAskedDate Asked Response RatingCategoriesRelationships:Moderator(Moderator ID) -> SurprisePrompt(ModeratorID)Evento(EventoID) -> MonthlyPrompt(EventID)Evento(EventoID) -> OngoingEvent(EventID)Evento(EventoID) -> Archives(EventID)QOTD(Responsible) -> Moderator(ModeratorID)Identify the primary and foreign keys for each relation (using appropriate notation). Maybe list the primary and foreign keys?Solution:Identify the primary and foreign keys for each relation (using appropriate notation). already identified the primary keys and foreign keys in the schema above, and used (Primary Key) and (Foreign Key) notations to specify their roles in the relations.Que) Identify and describe any indexes needed to speed up searches on non-key attributes – can you explain it too? So I understand why you came up with the answer, please?Solution:Indexes are typically created on columns that are frequently used for searching or filtering data to speed up query performance. In your schema:You may want to create an index on the Date Started column in the SurprisePrompt, MonthlyPrompt, OngoingEvent, and Archives tables since you might need to search for events based on their start dates.An index in the Discord Username column in the Moderator table can be helpful for quickly looking up moderators by their Discord usernames.You might also consider an index in the Responsible column of the QOTD table if you frequently search for questions by the person responsible.Que) Identify and describe unique, conditional (check), non-null, referential integrity, or other constraints needed to guarantee the integrity of the database.Solution:Identify and describe unique, conditional (check), non-null, referential integrity, or other constraints needed to guarantee the integrity of the database.In your schema:Ensure that the Moderator ID in the Moderator table is unique to maintain data integrity.The Moderator ID and Event ID columns in related tables should have ID foreign key constraints referencing the corresponding primary key columns.You may want to enforce constraints to ensure that certain columns cannot have NULL values, such as Question in the QOTD table or DiscordUsername in the Moderator table.Conditional constraints may be applied to ensure that data follows specific rules or patterns. For example, you can enforce constraints on dates to ensure they are in a valid format and within certain ranges.Que) Describe the set of business or workflow rules applicable to your project. Next, describe at what point in the workflow you will implement the business or workflow logic and the justification for doing so.Solution:The project involves managing a Discord community focused on artistic activities and engagement. Some possible business or workflow rules could include:Assigning a moderator to a specific week or event.Ensuring that a moderator's schedule does not overlap with another event they are responsible for.Tracking the usage history of prompts and questions.Keeping a record of member participation and response ratings for various activities.These rules should be implemented at the point of data entry and management, such as when adding or updating moderators, events, prompts, or questions. Implementing these rules in your database ensures data accuracy and consistency, which is crucial for maintaining a well-organized and engaged community.Justifications for implementing these rules include improving community engagement, content planning, and efficient event management. By enforcing these rules, you can ensure that the right moderators are assigned to events, that there are no scheduling conflicts, and that you have accurate data to analyze and plan future activities.the logical database design for the project, focused on managing an artistic Disney community, has been successfully structured into normalized relations, defined primary and foreign keys, identified potential indexes, and described constraints to ensure data integrity. The implementation of these design elements aligns with the project's objectives of enhancing community engagement, content planning, and efficient event management, ultimately contributing to a well-organized and thriving community.