[solved]-Using Notepad Write Create Table Sql Statements Part 2 Code Insert Sql Statements Enter Da Q39050701
using a notepad++
write CREATE TABLE SQL statements
Part 2) Code the INSERT INTO SQL statements to enter data foryour 3 favorite books. You may need to research them a bit to fillout the necessary fields. Enter the necessary and associated datainto all your database tables. Enter at least one book that isauthored by more than one author. This may require up to 16 rows ofdata – though it could be less than that (e.g. if all your booksare published by the same publisher or are from the same genre.(Also, you may take some liberties to make up some of the data, ifyou are unable to easily locate it.) Add these INSERT INTOstatements into your script file (created in part 1). Note that theorder in which you insert the data – is also important. Be sure topay attention to the “referential integrity rules” as you enter thedata. For example – the Book record that you insert will need tohave a valid GenreID and PubID.
Part 3) Insert SPOOL statements into the script file created inParts 1 and 2 to direct all the output of your execution to a textfile. Capture the output from an error-free execution to a spoolfile named: yourLastName_A3Spool.txt. Load and execute the scriptfile. If it doesn’t execute correctly the first time, correct anyerrors, delete (DROP) tables (if necessary) and re-run your scriptuntil it runs error free and produces an error free spool file.
Part 4) From Developer’s SQL window, write and execute theSELECT * FROM table statement, replacing table with the actualtable name, to list the data in each of the 5 tables. Capture theoutput from each of these 5 SELECT statements – by snipping theoutput window and copying/pasting it into a Word Document calledyourLastName_A3Selects.docx. Save the Word document. Label thesnippets to clearly identify what you snipped
Expert Answer
Answer to using a notepad++ write CREATE TABLE SQL statements Part 2) Code the INSERT INTO SQL statements to enter data for your 3… . . .
OR
