Create a database

You must create the following script files in MSSMS; to do this select Save from the File menu when you have finished typing the necessary code and save it to disk. Script files should have a .SQL file extension.

Complete the following:

• Use the given initial ER diagram
• Create a script file that includes the code for creating the database and all of the tables required in the project. PRIMARY KEY, FOREIGN KEY, UNIQUE and CHECK constraints must be included. Make use of the IDENTITY property, DEFAULT values and constraints. Remember that master/parent tables must be created first.
• Create a script file to insert data into your user-created tables. Add at least four records for each table without foreign keys and seven records for each table that does contain a foreign key.
• Create a script file to create the views as specified.
• Create a script file to create the stored procedures as specified.
• Create a script file to create at least two triggers for your project. There are no specifications for what types of triggers you must create. You should apply your knowledge and create triggers that you think would be appropriate.
• Create a script file to delete the database that you create.
• Create appropriate indexes on your tables.
• You should validate all applicable arguments in the stored procedures where arguments are received.
• Make use of iteration where appropriate.
• Using the GUI (Graphical User Interface), create a full backup of your database and send it to a zipped folder.
• Each script file must have a header section (using comments) that contains the following information:
  • Script file name
  • Programmer name (Clara Hammann)
  • Date
  • A short description of what the script file does
• When commenting your code, both styles of commenting (– or /* */) may be used. Just remember to maintain consistency throughout your project.
• Save all of the script files together with the backup onto a disk and hand it in with printouts of the script files. Provide clear instructions in your user documentation on how to execute the views and stored procedures, including the arguments that need to be passed to the stored procedures. In your user documentation you should include author and date details, together with the purpose and description of the project.