Design and Implement a small $$database$$ using Microsoft SQL Server.

Remember that you are really not creating a $$database$$ but rather a collection of tables that we will call a $$database$$ the tables should have a common theme

Some database ideas: Course Manager, Payroll, Inventory, Restaurant Management, Game Collection. Some have used this project to create databases that are useful to them in their everyday lives $($one student created a Java$-$based database he used as a Boy Scout Leader, another used it to keep track of skiing slopes, and yet another used it to track his lawn mowing business$)$

CREATE script $($similar to create script I put in folder with samples$)$ for me to run to create your database. The script should not only CREATE ALL THE TABLES for your database BUT also should POPULATE YOUR TABLES $($that is$,$ insert all the rows of data into your tables$).$ Make sure you have $10$ or more rows of data in your tables so I can get the feel of your database theme!

$3$ or more tables should be created. Make sure there are relationships between your tables $($think about how they are connected to one another$).$

DELETE script $($similar to delete script I put in folder with samples$)$ that I can run to delete your database tables.

Create several user$-$defined stored procedures $($you must write them in T$-$SQL since we are using Microsoft SQL Server and that is what I will use to test them$)($see references in folder $$ from week $9$; I have also attached samples of code $$ this is similar to writing Java methods and then you $$call$$ them $$ I will be executing them to do something $$ insert ski resort, delete customer,...$)$

At least $3$INSERT$$ STORED PROCEDURES that can be called to INSERT records into your different tables $$ the more, the better the grade!

At least $3$DELETE$$ STORED PROCEDURES that can be called to DELETE records from your different tables $$ the more, the better the grade!

At least $3$UPDATE$$ STORED PROCEDURES that can be called to UPDATE records in your different tables $--$ the more, the better the grade!

MAKE YOUR DATABASE your UNIQUE DESIGN $$ creating the exact same tables that we used for the sample databases is not sufficient and I will penalize for your lack of creativity.

Create a design document $$ make it $1$ or $2$ pages to describe your database and what kind of tables and stored procedure are in it $.$ There is no formal design template for this; just consider it a document that explains what you made for your database $$ ideas: E$-$R diagram, explanations of stored procedures with example usage.