Create a login and database user Sam. If you get a $$server principal already exists$$ error you know from our video on Authentication that a login Sam already exists. If that is the case you will need to use a different login than Sam. The new login needs to be unique $$ I would suggest your firstname$\_$lastname. Sam $($or your own database user name$)$ should have select, delete, insert, and update authorization to all tables in your database. Sam $($or your own database user name$)$ should not have access to change the structure of the tables in your database.

Create a login and database user Jane. If you get a $$server principal already exists$$ error you know from our video on Authentication that a login Jane already exists. If that is the case you will need to use a different login than Jane. The new login needs to be unique $$ I would suggest your firstname$\_$lastname. Jane $($or your own database user name$)$ should have read authorization to all the tables in your database. Jane $($or your own database user name$)$ should only have delete, insert and update authorization to the student table. Jane $($our your own database user name$)$ should not have delete, insert and update authorization to any other tables.