You are setting up a kiosk in a library that hundreds of people will access every month. You want to make sure visitors to library have access to read data from the SQL Server, but they should not be able to change any of the data. You need to accomplish this with the least administrative overhead possible. What should you do?

You are setting up a kiosk in a library that hundreds of people will access every month. You want to make sure visitors to library have access to read data from the SQL Server, but they should not be able to change any of the data. You need to accomplish this with the least administrative overhead possible. What should you do?

You are setting up a kiosk in a library that hundreds of people will access every month. You want to make sure visitors to library have access to read data from the SQL Server, but they should not be able to change any of the data. You need to accomplish this with the least administrative overhead possible. What should you do?


Answer: – Enable the guest user account in Windows, and map it to a SQL login. No database user account named guest will beed to be created because it already exists in each database. Add the guest account to the db_denydatawrited and db_datareader roles.

(Creating a user account especially for this application is possible but hard to manage, especially when a database user account already exists for each database. Therefore, creating a user login for the guest account is the easiest way to allow access to the kiosk.)