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.