Database

Need Help in Database Assignment?
We can help you if you are having difficulty with your Database Assignment. Just email your Database Assignment at admin@assignmentcache.com.
We provide help for students all over the world in Database Assignment.

Items 1 to 10 of 16 total

per page
Page:
  1. 1
  2. 2

Grid  List 

Set Descending Direction
  1. Part 4 Adult Baseball league Data Model MySQL Workbench

    Types of Relationships and Sample Databases

    Regular Price: $20.00

    Special Price: $15.00

    Types of Relationships and Sample Databases

    Part 2
    Come up with an original example of a one to many unary relationship. Create an example model of this relationship using the MySQL Workbench data modeler.

    Part 3
    Come up with an original example of a ternary relationship. Create an example model of this relationship using the MySQL Workbench data modeler.

    Part 4
    Using MySQL Workbench – create a data model for on Adult Baseball league which supports all of the following data requirements:
    Teams
        A team has a unique number associated with it
        Team Name
        Team City
        Each team has more than one player associated with it

    Players
        Each Player has a unique number
        A player may play or have played for more than one team
        The number of years and batting average is tracked for each team the player played for.

    Coaches
        In this league, all coaches are also players.
        A Team can have more than one coach.

    Bats
        A team can have multiple bats
        Each bat is identified by a unique serial number.

    For each of the three models above, you should export your model as a single page PDF and submit the resulting files.

    Learn More
  2. MIS582 iLab 1 SQL Queries Using MySQL Select Statements

    MIS582 iLab 1 SQL Queries Using MySQL

    Regular Price: $15.00

    Special Price: $12.00

    MIS582 iLab 1 SQL Queries Using MySQL


    iLab Overview
    Scenario/Summary
    The purpose of this iLab is to prepare for the first phase of the Course Project. This week, you will learn to create and run SQL SELECT queries from a script in the MySQL database. You will need to create a database in MySQL via Omnymbus, run a SQL script to create tables and insert data, create and execute a script containg SQL SELECT queries using the STUDENT table.
    Please ensure that you can connect to MySQL/Omnymbus via the account your Professor has emailed to you. Please consult with the document titled MySQLOmnymbusSupport.docx located in the Doc-Sharing folder titled Omnymbus Tutorial Files for instructions on how to get help for any issues that you are having with the MySQL/Omnymbus Environment.
    Due Midnight Mountain Time attached to the Week 1 DropBox. OR let me know if you are going to be delayed!
    SQL file named Lab1_Query.sql containing SELECT statements
    Text document named Lab1_Output.txt containing labeled output
    Upload files to the Week 1 iLab Dropbox.
    Please do not zip the files


    Required Software
    Omnymbus – MySQL at the edupe database server.
    Access the software at https://devry.edupe.net:8300
    If you have any problems, connection, password, technical, etc ONLY your instructor can assist. Using any other Help facility will delay the resolution of the problem as the request is forwarded in all cases to the instructor.


    STEP 1: Logging in to Omnymbus
    Look at your email account to obtain the MySQL/Omnymbus account and password that your Professor has emailed to you.
    To help you log into MySQL Omnymbus environment, download the tutorial Login MySQL Omnymbus Environment in the Doc-Sharing folder titled "Omnymbus Tutorial Files".


    STEP 2: Create a Database and modify your script to reference your Database
    Create a MySQL database:
    Download the tutorial Creating a Database in MySQL Omnymbus Environment from the folder in Doc-Sharing titled Omnymbus Tutorial Files. Follow the steps to create a database in MySQL, especially paying attention to the database naming conventions specified in the tutorial.
    Download the Wk1LoadDatabaseScript.sql file from Doc Sharing in the folder titled iLab Documents.


    STEP 3: Running script file in MySQL, create SQL
    Download the tutorial Running SQL Scripts in MySQL Omnymbus environment from the folder in Doc-Sharing titled Omnymbus Tutorial Files. Follow those steps and execute the Wk1LoadDatabaseScript.sql file to create the tables and to insert data into them; and then download and run the script file with the queries iLab1QueryScript.sql. This script has the first few queries and it is intended that you should finish it. A demonstration in the Week 1 Live Lecture will be provided.


    Create SQL SELECT Queries:
    ALWAYS and only use a plain text editor such as Notepad! All word processors will insert hidden tags that confuse database processors.
    Using the data in the Student table in the database, expand the supplied starter SQL script file named iLab1QueryScript.sql, containing queries to execute each of the tasks below.
    To reference, learn and apply MySQL's own dialect of the SQL language to this iLab, browse through the file M10C_KROE8352_13_SE_WC10C.pdf in the Doc-Sharing folder titled My SQL Documents.
    Save the completed results by copying and pasting to a file named iLab1_Results.txt
    An incomplete example is provided in the Doc Sharing.


    Query1
    Write a SQL statement to display Student’s First and Last Name.


    Query2
    Write a SQL statement to display the Major of students with no duplications. Do not display student names.


    Query3
    Write a SQL statement to display the First and Last Name of students who live in the Zip code 82622


    Query4
    Write a SQL statement to display the First and Last Name of students who live in the Zip code 97912 and have the major of CS.


    Query5
    Write a SQL statement to display the First and Last Name of students who live in the Zip code 82622 or 37311. Do not use IN.


    Query6
    Write a SQL statement to display the First and Last Name of students who have the major of Business or Math. Use IN.


    Query7
    Write a SQL statement to display the First and Last Name of students who have the Class greater than 1 and less than 10. Use the SQL command BETWEEN.


    Query8
    Write a SQL statement to display the First and Last Name of students who have a last name that starts with an S.


    Query9
    Write a SQL statement to display the First and Last Name of students having an a in the second position of their first names.


    Query10
    Write a SQL expression to display each Status and the number of occurrences of each status using the Count(*) function; display the result of the Count(*) function as CountStatus. Group by Status and display the results in descending order of CountStatus.
    Note: there are examples very similar to these in the Kroenke text


    Rubric
    Queries that are correct will be awarded the number of points shown below:
    4 points: Query 1
    5 points: Query 2 – 9
    6 points: Query 10
    The following rubrics will be used for incorrect queries:
    0 points: Query was not turned in with the assignment.
    -4 points: Query will not run.
    -3 points: Query runs but is incorrect because query required a WHERE clause to meet requirements which was not included.
    -2 points: Query runs but is incorrect because WHERE clause contained errors, gives popup for user input, or only meets partial requirements.


    Please Make sure all requirements are met!

    Learn More
  3. MIS582 Course Project Week 2 SQL Queries Using MySQL Select Statements.jpg

    MIS582 Course Project Week 2 SQL Queries Using MySQL

    Regular Price: $15.00

    Special Price: $12.00

    MIS582 Course Project Week 2 SQL Queries Using MySQL


    The Course Project will consist of three tasks, each worth 50 points due in Weeks 2, 4, and 6. Successful completion of the iLabs will help you in completing the project tasks.


    Week 2: Task1: SQL Queries Using MySQL (50 Points)
    Using the same tables that you created by running the script file provided in Doc Sharing for iLab1, write
    the following 10 queries each worth 5 points.


    Name Task
    Query1: Write a SQL statement to display the course numbers of classes taught by Hammett Glenn.
    Query2: Write a SQL statement to display the course names of the courses taught by an instructor whose id is 415.
    Query3: Write a query to display the name and office number of all instructors who teach Psy101.(USE NATURAL JOIN)
    Query4: Write a query to display the semester and the number of courses offered in that semester. Display only the semesters that offer more than five courses.
    Query5: Write a SQL statement to display the name of each campus and the total number of rooms in that campus.
    Query6: Write a SQL statement to display the list of instructors who are approved as well as those who are not approved. (OUTER JOIN)
    Query7: Write a SQL statement to display the start date and start time of all classes taught by instructor Hammett Glenn.
    Query8: Write a SQL statement to display the number of students in each major with a status of failing.
    Query9: Write a SQL statement to display the credit hours of all courses that Hammett Glenn is approved to teach.
    Query10: Get the campus name and phone number of all rooms with numbers greater than 25.


    Deliverables
    Create and save your SQL queries and script in a text file named Lastname_Task1_SQL_Script.sql.
    Capture the output and paste it into Word Document. Save it as Lastname_Task1_SQL_Result.txt.
    When you are done, submit your documents zipped together in a single file to the Week 2: Course Project Week 2 Task 1 Dropbox.


    Rubrics
    Queries that are correct will be awarded the number of points shown below:
    4 points: Query 1
    5 points: Query 2–9
    6 points: Query 10
    The following rubrics will be used for incorrect queries.
    0 points: Query was not turned in with the assignment.
    -4 points: Query will not run.
    -3 points: Query runs but is incorrect because query required a WHERE clause to meet requirements which was not included.
    -2 points: Query runs but is incorrect because the WHERE clause contained errors, gives popup for user input, or only meets partial requirements.
    Tutorials to Consult With M10C_KROE8352_13_SE_WC10C.pdf in the folder titled My SQL Documents in Doc Sharing for all things to do with MySQL including example SQL.
    Login MySQL Omnymbus Environment.docx in the folder titled Omnymbus Tutorial Files in Doc Sharing for how to log into the Omnymbus Environment.
    Creating a Database in MySQL Omnymbus Environment.docx in the folder titled Omnymbus Tutorial Files in Doc Sharing for how to create a Database in the Omnymbus Environment. Remember, all work must be done under a database you first create.
    Running SQL Scripts in MySQL Omnymbus Environment.docx in the folder titled Omnymbus Tutorial Files in Doc Sharing for how to create and run your SQL Scripts.

    Learn More
  4. MIS582 iLab 3 Week 5 Database Construction Using MySQL SQL script file named LastName_Wk5

    MIS582 iLab 3 Week 5 Database Construction Using MySQL

    Regular Price: $15.00

    Special Price: $12.00

    MIS582 iLab 3 Week 5 Database Construction Using MySQL


    iLAB OVERVIEW
    Scenario/Summary
    In this assignment, you will learn to create a database schema from a given ERD. To complete this assignment, you will need to be able to run a script in MySQL.
    Please ensure that you can connect to MySQL on the Omnymbus edupe web server.
    Contact your instructor for assistance for any issues that you are having with the MySQL/edupe environment.


    Deliverables
    SQL script file named LastName_Wk5.sql. That is a txt document with the .sql extension. It is a script of SQL commands that executes in a MYSQL environment.
    A text document named LastName_Wk5_Output.txt which is a copy of the results obtained when the SQL command script it run. The Instructor must be able to run our script and obtain identical results.
    When you are done submit them to the Week 5: iLab Dropbox. Files that have been opened or processed by any software other than Notepad are not acceptable. Zipped files are not acceptable and may be returned ungraded.


    Required Software
    MySQL in the edupe environment. SQLZOO may be used to test the scripts.
    Access the software at https://devry.edupe.net:8300.
    Steps 1–8 iLAB STEPS


    STEP 1: Entity Relationship Diagram Analysis
    Review the ERD below to understand the entities, attributes, primary keys, and relationships that you will create in your MySQL database.
    STEP 1: Create a New Database
    • Create a new database following the naming conventions we are using for our databases, as specified in the tutorial file Creating a Database within MySQL.pdf listed in the doc-sharing folder titled “Omnymbus Tutorial Files” in Doc-Sharing. All of our work in this iLab, will be done under this database.


    STEP 2: Create SQL File
    • To reference, learn and apply MySQL’s own dialect of the SQL language to this iLab, browse through the file M10C_KROE8352_13_SE_WC10C.pdf in the Doc Sharing folder titled My SQL Documents.
    • Create a script file named LastName_Wk5.sql containing SQL statements created in Steps 3–7 below.
    • But first include the following commands at the top of your script:
    o SET FOREIGN_KEY_CHECKS=0;
    o DROP TABLE IF EXISTS STUDENT;
    o DROP TABLE IF EXISTS CAMPUS;
    o DROP TABLE IF EXISTS ROOM;
    o DROP TABLE IF EXISTS COURSE;
    o DROP TABLE IF EXISTS INSTRUCTOR;
    o DROP TABLE IF EXISTS APPROVED_INSTRUCTOR;
    o DROP TABLE IF EXISTS CLASS;
    o DROP TABLE IF EXISTS STUDENT_GRADE;
    o SET FOREIGN_KEY_CHECKS=1;


    STEP 3: Add Tables, Set Primary Keys and Foreign Keys
    Add tables to the MySQL database.
    • Add a table for each entity listed in the provided ERD diagram.
    • Add a column for each attribute listed in the provided ERD diagram.
    • Select primary key for each table as indicated in the provided ERD diagram.
    • Identify foreign key relationship between tables as indicated in the provided ERD diagram.
    • Enable referential integrity on the relationship.
    • Enable cascade updates on the relationship.


    STEP 4: Set Data Types for Table Fields
    For every column in every table, update the data type as needed to enforce the domain constraints of the data.
    • Dates should have a date data type.
    • Surrogate keys should be auto-numbered.
    • Numeric data should have a numeric data type.
    • Character data should have a character data type.


    STEP 5: Set Column Constraints
    Set the following column constraints in your database.
    • Student first and last name cannot be a null value.
    • Course credit hours must be between one and four.
    • Course name must be unique and cannot be a null value.
    • Instructor first and last name cannot be a null value.
    • Grade must be one of these values: A, B, C, D, F, I, W, or E. W signifies withdrawn and E signifies enrolled.


    STEP 6: Add Data to Tables
    Write INSERT statements to add at least 2–3 rows of data to each table in your database. Use any values that you like for each of the columns. Remember that you must add data to parent tables before adding data to child tables, because referential integrity is enabled.
    HINT – Do not spend any lengthy amount of time on the INSERTs. This data has no use other than making sure the CREATE ran correctly.


    STEP 7: Run the Script
    • Include a COMMIT command at the end of the script.
    • Include SHOW TABLES command at the end of the script, to show all tables created.
    • Include SELECT statements for each table at the end of the script, to show data inserted.
    • Give your script a run, by uploading into Omnymbus and executing it just like you did in iLab1.
    • Paste a copy of the output in a Notepad document named LastName_Lab3_Output.TXT


    Step 8: Save and Upload to Dropbox
    When you are done, submit the following files to the Week 5: iLab Dropbox:
    • LastName_Wk5.sql A text file you created with Notepad
    • LastName_Wk5_Output.txt A text file created by copy and paste from edupe.


    Rubric
    Points will be awarded according to the following rubrics.
    • 5 points: Table created for each entity in the provided E-R model
    • 5 points: Column created for each attribute in the provided E-R model
    • 5 points: Primary key added for each table with unique constraints specified as column properties
    • 5 points: Data type set for each attribute
    o Dates should have a date data type.
    o Surrogate keys should be autonumbered.
    o Numeric data should have a numeric data type.
    o Character data should have a character data type.
    • 10 Points: Relationships created as shown on the provided E-R model
    o Relationships enabled for referential integrity
    o Relationships enabled for cascade updates.
    • 10 Points: At least two rows of data added for each table
    • 10 Points: Column constraints added as indicated in project description, checked by adding rows to data with invalid values
    o Student name cannot be set to null.
    o Course credit hours are restricted to between one and four.
    o Course name must be unique and cannot be set to null.
    o Instructor last name and first name cannot be set to null.
    o Grade is restricted to be one of these values: A, B, C, D, F, I, W, or E (enrolled).

    Learn More
  5. MIS582 iLab Week 7 the 4th of 4 Webserver Database server Construction Using MySQL and INDEX PHP

    MIS582 iLab 4 Week 7 Webserver/Databaseserver Construction Using MySQL and PHP

    Regular Price: $15.00

    Special Price: $12.00

    MIS582 iLab 4 Week 7 Webserver/Databaseserver Construction Using MySQL and PHP


    iLab Overview
    Scenario/Summary
    In this assignment learn to create and manipulate a MySQL database using the PHP. To complete this assignment, you will need to be able to run MySQL via Omnymbus. You should review Chapter 11's coverage on PHP, the tutorial titled "PHP and MySQL" listed in the Webliography and MySQL's own dialect of the SQL language via the file M10C_KROE8352_13_SE_WC10C.pdf in the Doc-Sharing folder titled My SQL Documents.
    Please ensure that you can connect to MySQL/Omnymbus via the account your Professor has emailed to you. Please consult with the document titled MySQLOmnymbusSupport.docx located in the Doc-Sharing folder titled Omnymbus Tutorial Files for instructions on how to get help for any issues that you are having with the MySQL/Omnymbus Environment.


    Deliverables
    Submit your assignment to the Dropbox, located at the top of this page. For instructions on how to use the Dropbox, read these step-by-step instructions. (See the Syllabus section "Due Dates for Assignments & Exams" for due dates.)
    Name your MySQL database Lab4_xxxx where xxxx is your userid. Create and save your MySQL database file. You will be required to submit a web-link to your index.php file, along with 6 php script files and a sql file that will be executed from the Omnymbus public Web page from your Omnymbus account. Please note that your php and sql files will be based upon the templates provided the zip file titled MIS582_Wk7_templates.zip located in the folder titled iLab Documents in Doc Sharing.
    You will need to modify the following php scripts and sql file from the MIS582_Wk7_templates.zip file.
    • index.php
    • insert.php
    • insert_data.php
    • update.php
    • update_data.php
    • delete.php
    • MyAddressBook_CreateTable.sql


    Required Software
    Omnymbus – MySQL
    Access the software at https://devry.edupe.net:8300.


    Lab Steps
    STEP 1: Review the Data Dictionary
    Review the provided data dictionary below to understand the entity, attributes, and primary key of the supplied MySQL database.
    Table Name ATTRIBUTE NAME CONTENTS TYPE FORMAT RANGE REQUIRED PK or FK
    MyAddressbook id Contact ID Number Auto-Increment
    Int(3) 999 000-999 Y PK
    f_name Contact First Name VCHAR(25) Xxxxxx Y
    L_name Contact Last Name VCHAR(25) Xxxxxx Y
    ADDRESS Contact Address VCHAR(25) Xxxxxx Y
    City Contact City VCHAR(25) Xxxxxx 0-9 Y
    State Contact State CHAR(2) Xxxxxx Y
    zip Contact Zip Code NUMBER(5) 99999 Y
    phone Contact Phone NUMBER(10) 9999999999 Y

    STEP 2: Create Table, Insert Statement
    • Run MySQL via Omnymbus.
    • Modify the table creation script that will be used to create the database with the outlined attributes from the Data Dictionary.
    • Provide one Insert Statement that will add your contact information to the newly created table.
    • Save the file with a name containing Lab7_, your first initial, and your last name (e.g., Lab7_JSmith.sql).
    • Execute your script and ensure that the database is created.


    STEP 3: Build Index PHP Page
    Building Your index.php Web Page
    In this step, you will complete your php script page to connect to the Lab7 database and display the MyAddressbook table on the Web page.
    • Complete the MySQL connection for the index.php page. Be sure to fill in appropriate host (127.0.0.1), username, password, and database information in the mysqli field.
    • Modify the provided php code to display each attribute of your MyAddressbook table. Note that initially, only 1 entry should be present in your table.
    • Save your index.php file in your public_html folder in Omnymbus file manager.
    • Please note that you will find your public_html folder down the path zdisk/USERID/public html
    • Direct your Web browser to your site url (ex. http://devry.edupe.net/~XXXX/index.php).
    • Note that you’ll replace XXXX with your Omnymbus login ID.
    • Ensure that your file executes and the database table displays on the screen.
    • If you have a correct connect command but you get the error message "MySQL ERROR 1045 (28000): Access denied for user" you will have to create a new password with the box "Change password in other modules?" checked.
    • There is a supplied image in the Doc Sharing that provides an example of how your index.php page should look. Note: Feel free to add any additional formatting or images to your index.php page.

    STEP 4: Build, Update PHP Pages
    Building Your update.php and update_data.php Pages
    In this step, you will complete two php HTML pages. Your update.php page will provide a form for users to submit data to the database that will be updated. The update_data.php page will provide the actual queries in php to update the data in your database. When this process is complete, your page will redirect the user back to the index.php page.
    • Review the update_data.php page template.
    • You will need to modify the php code to add additional input forms for the user to enter all appropriate attributes that will need to be updated.
    • In the update_data.php file, ensure that your <form action> tag is set equal to update.php
    • Character data should have a character data type.
    • When the action is complete, your page should redirect back to index.php.


    STEP 5: Build Delete PHP Page
    Building Your delete.php Page
    In this step, you will complete the delete.php page. Your delete.php page will process the query that will remove the necessary data for the database. When this process is complete, your page will redirect the user back to the index.php page.
    • Review the delete.php page template.
    • You will need to modify the php code to delete the provided entry based on the address id.
    • When the action is complete, your page should redirect back to index.php.


    STEP 6: Test Links to Update, Delete, and Insert Pages. Submit Deliverables.
    Finishing Your Web-Enabled Database
    Before submitting, ensure that you have added at least 5 entries to your Addressbook database.
    Ensure that all links for update, delete, and insert work properly.
    When you are done, submit your web-link to your index.php (e.g. http://devry.edupe.net/~####/index.php), If your web pages do not work according to the rubric below you can submit a zip file titled Lab4_FirstInitialLastName.zip which should contain your six php code pages and your database script for possible partial credit,
    Rubric
    Points will be awarded according to the following rubrics.
    • 10 points: Script and Table created for the MyAddressbook entity as described in the Data Dictionary.
    • 10 points: index.php created that correctly displays the contents of the database.
    • 10 points: insert.php and insert_data.php pages created that correctly add data to the database.
    • 10 points: update.php and update_data.php pages created that correctly update the data in the database.
    • 10 Points: delete.php page created that correctly removes an entry from the database.
    For a more advanced optional lab experience you can add error checking and comments and better appearance to the code. Use Chapter 11 as a guide.

    Learn More
  6. Murach's MySQL 3rd Edition Chapter 14 Exercise 1

    Murachs MySQL 3rd Edition Chapter 14 Exercise 1 and 2

    Regular Price: $12.00

    Special Price: $10.00

    Murach's MySQL 3rd Edition Chapter 14 Exercise 1 and 2


    1. Write a script that creates and calls a stored procedure named test. This procedure should include a set of three SQL statements coded as a transaction to reflect the following change: United Parcel Service has been purchased by Federal Express Corporation and the new company is named FedUP. Rename one of the vendors and delete the other after updating the vendor_id column in the Invoices table.
    If these statements execute successfully, commit the changes. Otherwise, roll back the changes.


    2. Write a script that creates and calls a stored procedure named test. This procedure should include a set of two SQL statements coded as a transaction to delete the row with an invoice ID of 114 from the Invoices table. To do this, you must first delete all line items for that invoice from the Invoice_Line_Items table.
    If these statements execute successfully, commit the changes. Otherwise, roll back the changes.

    Learn More
  7. Murachs MySQL 3rd Edition Chapter 15 Exercise 2

    Murachs MySQL 3rd Edition Chapter 15 Exercise 1 and 2

    Regular Price: $12.00

    Special Price: $10.00

    Murachs MySQL 3rd Edition Chapter 15 Exercise 1 and 2


    1. Write a script that creates and calls a stored procedure named insert_glaccount. First, code a statement that creates a procedure that adds a new row to the General_Ledger_Accounts table in the AP schema. To do that this procedure should have two parameters, one for each of the two columns in this table. Then, code a CALL statement that tests this procedure. (Note that this table doesn't allow duplicate account descriptions.)


    2. Write a script that creates and calls a stored function named test_glaccounts_description. First, create a function that tests whether an account description is already in the General_Ledger_Accounts table. To do that, this function should accept one parameter for the account description, and it should return a value of 1 if the account description is in the table or 0 if it isn't. (Note: If a SELECT statement doesn't return any data, it raises a NOT FOUND condition that your function can handle.)

    Learn More
  8. MySql DBA Project 2

    MySql DBA Project 2

    Regular Price: $20.00

    Special Price: $15.00

    MySql DBA Project 2


    Sometimes a search isn't thorough. For example, when looking for information on guitars, a user may search for the term "guitars" and potentially miss documents containing the word "Fender" (a type of guitar).


    MySQL's solution to this problem is the WITH QUERY EXPANSION option. The syntax for this solution is as follows:


    SELECT Title, AlbumDescription FROM Albums
    WHERE MATCH (AlbumDescription)
    AGAINST ('guitars' WITH QUERY EXPANSION);


    When you use WITH QUERY EXPANSION, MySQL actually searches your full text index twice. The first time it searches with the word guitars. It then takes the most relevant results from the first search, and searches again. Take a look:


    mysql> SELECT Title, AlbumDescription FROM Albums
    -> WHERE MATCH (AlbumDescription)
    -> AGAINST ('guitars');
    +---------------------+------------------------------------------+
    | Title | AlbumDescription |
    +---------------------+------------------------------------------+
    | Blood on the Tracks | Recorded using Martin and Fender guitars |
    +---------------------+------------------------------------------+
    1 row in set (0.00 sec)


    mysql> SELECT Title, AlbumDescription FROM Albums
    -> WHERE MATCH (AlbumDescription)
    -> AGAINST ('guitars' WITH QUERY EXPANSION);
    +----------------------+------------------------------------------+
    | Title | AlbumDescription |
    +----------------------+------------------------------------------+
    | Blood on the Tracks | Recorded using Martin and Fender guitars |
    | Highway 61 Revisited | First using the fender! |
    +----------------------+------------------------------------------+
    2 rows in set (0.00 sec)


    In the second query, the first row was matched by guitars, and the word fender was used to find the second row.


    Demonstrate WITH QUERY EXPANSION by writing four new subqueries against your Albums table. In your first two queries, do not use WITH QUERY EXPANSION. In the remaining two queries DO use WITH QUERY EXPANSION.


    Combine the results of the four subqueries with a UNION. Add a column to the result set called QueryExpansion that indicates which row used query expansion. Also, add a column called Query to the result to indicate which words were included in your search.


    Save your query as dba1lesson11project2.sql and then hand in the project.

    Learn More
  9. CS371 Database Design Week 5 Chapter 6 Exercise 1

    CS371 Database Design Week 5 Assignment Chapter 6 Questions

    Regular Price: $20.00

    Special Price: $15.00

    CS371 Database Design Week 5 Assignment Chapter 6 Questions

    Chapter 6 Exercises 1 page 154: Use MySQL Workbench to construct the relational diagram for this database.
    Chapter 6 Exercises 2 page 154: Use MySQL Workbench to construct the relational diagram for this database.
    Chapter 6 Exercise 5 page 155: Submit responses in Word Doc format.

    You may submit a single word doc with SQL queries and your models pasted in – OR – submit separate files including PDFs of your models and a word doc with your queries.

    Chapter 6 Exercise 1 page 154: Use MySQL Workbench to construct the relational diagram for this database:

    1.  Leslie’s Auto Sales has a relational database with which it maintains data on its salespersons, its customers, and the automobiles it  sells. Each of these three entity types has a unique attribute identifier.
    The attributes that it stores are as follows:
    • Salesperson Number (unique), Salesperson Name, Salesperson Telephone, Years with Company
    • Customer Number (unique), Customer Name, Customer Address, Value of Last Purchase From Us
    • Vehicle Identification Number (unique), Manufacturer, Model, Year, Sticker Price Leslie’s also wants to keep track of which salesperson sold
    which car to which customer, including the date of the sale and the negotiated price. Construct a relational database for Leslie’s Auto Sales.

    Answer:


    Chapter 6 Exercise 2 page 154: Use MySQL Workbench to construct the relational diagram for this database.

    2.  The State of New York certifies firefighters throughout the state and must keep track of all of them, as well as of the state’s fire departments. Each fire department has a unique department number, a name that also identifies its locale (city, county, etc.), the year it was established, and its main telephone number. Each certified firefighter has a unique firefighter number, a name, year of certification, home
    telephone number, and a rank (firefighter, fire lieutenant, fire captain, etc.) The state wants to record the fire department for which each firefighter currently works and each firefighter’s supervisor. Supervisors are always higher-ranking certified firefighters.
    Construct a relational database for New York’s fire departments and firefighters.

    Answer:


    Chapter 6 Exercise 5 page 155: Submit responses in Word Doc format.

    5. In the General Hardware Corp. database of Figure 6.1, what would happen if:
    a. The delete rule between the CUSTOMER and CUSTOMER EMPLOYEE relations is restrict and an attempt is made to delete the record for customer 2198 in the CUSTOMER relation?
    b. The delete rule between the CUSTOMER and CUSTOMER EMPLOYEE relations is cascade and an attempt is made to delete the record for customer 2198 in the CUSTOMER relation?
    c. The delete rule between the CUSTOMER and CUSTOMER EMPLOYEE relations is set to null and an attempt is made to delete the record for customer 2198 in the CUSTOMER relation?
    d. The delete rule between the CUSTOMER and CUSTOMER EMPLOYEE relations is restrict and an attempt is made to delete the record for employee 33779 of customer 2198 in the CUSTOMER EMPLOYEE relation?
    e. The delete rule between the CUSTOMER and CUSTOMER EMPLOYEE relations is cascade and an attempt is made to delete the record for employee 33779 of customer 2198 in the CUSTOMER EMPLOYEE relation?
    f. The delete rule between the CUSTOMER and CUSTOMER EMPLOYEE relations is set-to-null and an attempt is made to delete the record for employee 33779 of customer 2198 in the CUSTOMER EMPLOYEE relation?

    Answer:

    Learn More
  10. CS371 Database Design Week 4 Chapter 5 Relational Model

    GU CS371 Database Design Week 4 Assignment Chapter 5 Relational Database Model

    Regular Price: $20.00

    Special Price: $15.00

    GU CS371 Database Design Week 4 Assignment Chapter 5 Relational Database Model


    The assignment comes from Chapter 5 Minicase 1 but includes an additional step:
    Using MySQL Workbench, create the relational data model for the database for happy cruise lines, which includes 6 tables. (Note: Be sure primary and foreign keys are correct). Export the PDF version of your model for submission.
    Then complete steps a – g. Note: On step g, provide correct SQL syntax for finding the result to each item i – viii. i.e. Do not use the informal relational approach – looking for valid, correct SQL as described in Chapter 4.
    You may submit a single word doc with SQL queries and your model pasted in – OR – submit 2 separate files including a PDF of your model and a word doc with your queries.


    Fundamentals of Database Management Systems 2nd Edition Chapter 5 Minicase 1
    1. Consider the following relational database for Happy Cruise Lines. It keeps track of ships, cruises, ports, and passengers. A “cruise” is a particular sailing of a ship on a particular date. For example, the seven-day journey of the ship Pride of Tampa that leaves on June 13, 2009, is a cruise. Note the following facts about this environment.
    Both ship number and ship name are unique in the SHIP Relation.
    A ship goes on many cruises over time. A cruise is associated with a single ship.
    A port is identified by the combination of port name and country.
    As indicated by the VISIT Relation, a cruise includes visits to several ports, and a port is typically included in several cruises.
    Both Passenger Number and Social Security Number are unique in the PASSENGER Relation. A particular person has a single Passenger Number that is used for all of the cruises that she takes.
    The VOYAGE Relation indicates that a person can take many cruises and a cruise, of course, has many passengers.


    SHIP Relation
    Ship Number
    Ship Name
    Ship Builder
    Launch Date
    GrossWeight


    CRUISE Relation
    Cruise Number
    Start Date
    End Date
    Cruise Director
    Ship Number


    PORT Relation
    Port Name
    Country
    Number of Docks
    Port Manager


    VISIT Relation
    Cruise Number
    Port Name
    Country
    Arrival Date
    Departure Date


    PASSENGER Relation
    Passenger Number
    Passenger Name
    Social Security Number
    Home Address
    Telephone Number


    VOYAGE Relation
    Passenger Number
    Cruise Number
    Stateroom Number
    Fare


    Additional step:
    Using MySQL Workbench, create the relational data model for the database for happy cruise lines, which includes 6 tables. (Note: Be sure primary and foreign keys are correct). Export the PDF version of your model for submission.


    Then complete steps a – g.
    Note: On step g, provide correct SQL syntax for finding the result to each item i – viii. i.e. Do not use the informal relational approach – looking for valid, correct SQL as described in Chapter 4.
    a. Identify the candidate keys of each relation.
    b. Identify the primary key and any alternate keys of each relation.
    c. How many foreign keys does each relation have?
    d. Identify the foreign keys of each relation.
    e. Indicate any instances in which a foreign key serves as part of the primary key of the relation in which it is a foreign key. Why does each of those relations require a multi-attribute primary key?
    f. Identify the relations that support many-to-many relationships, the primary keys of those relations, and any intersection data.
    g. Using the informal relational command language described in this chapter, write commands to:
    Note: On step g, provide correct SQL syntax for finding the result to each item i – viii. i.e. Do not use the informal relational approach – looking for valid, correct SQL as described in Chapter 4.
    i. Retrieve the record for passenger number 473942.
    ii. Retrieve the record for the port of Nassau in the Bahamas.
    iii. List all of the Ships built by General Shipbuilding, Inc.
    iv. List the port name and number of docks of every port in Mexico.
    v. List the name and number of every ship.
    vi. Who was the cruise director on cruise number 38232.
    vii. What was the gross weight of the ship used for cruise number 39482?
    viii. List the home address of every passenger on cruise number 17543.

    Learn More

Items 1 to 10 of 16 total

per page
Page:
  1. 1
  2. 2

Grid  List 

Set Descending Direction