Beginning ASP.NET 4.5 in CSharp and VB Opsylum

804 x APPENDIX B CONFIGURING SQL SERVER 2012
5. If you want to set fine-grained security options for your database objects, click the Securables
option visible in Figure B-6. This dialog box enables you to determine permissions for the
user account on objects in your database like tables, views, and stored procedures. For the
Planet Wrox website, you don’t need to make any changes in this dialog box.
6. Finally, click OK to create the database user and assign it to the db_datareader and db_
datawriter roles.
Now that SQL Server and your user accounts are configured correctly, the final step is to configure
the website to use this new user account.
1. Open the Web.config file of the Planet Wrox application from the C:\BegASPNET\Release
folder.
2. Modify the element so it ends up like this:
In your configuration file, each connection string should be on a single line. Don’t forget
to replace the value ServerName in the Data Source attributes with a valid server name.
Depending on your server and configuration, this could be as simple as (local) or .\
SqlExpress to point to a SQL Server on the local machine, DatabaseServer to point to a
server on the network called DatabaseServer, or something like DatabaseServer\Sql2012
that points to a named instance called Sql2012 on a machine called DatabaseServer.
3. Save the changes and then open the site by starting your browser and going to http://
localhost. Everything should still work as expected, but the site now no longer uses the
databases in the App_Data folder; it uses the SQL Server defined in your connection strings
instead through Windows Authentication, as identified by the Trusted_Connection=True
attribute in the connection string.
If you get an error when browsing to the site, you may need to turn off custom errors in the
Web.config file (or set it to RemoteOnly) to see the actual error message. Possible reasons
for the error are an incorrect server name in the connection string and an incorrectly configured
database role membership for the configured account.
Once you find out the correct account and have configured SQL Server correctly, using Windows
Authentication isn’t that hard. In fact, your connection string now becomes a little easier and more
secure, because you don’t need to store a username and password in it anymore.