SQL Server Web page project publication

Problem Description:

There will always be times in the work of this situation, in the development or QA program running is always good, but to the production environment, the program is not run out. The most impressive is the two Web page items that were previously encountered in SQL Server database, one to access the Web page error, and the other to have no results on the Drop-down list on the page.

Environment: SQL SERVER 2008, IIS, SSRS 2008, Visual Studio 2008, asp.net

　　Workaround:

In the first case:

After publishing the Web page to the production environment, the system detects whether your personal system login account has permission to access the page, which is configured in several tables in the database. After a classmate has configured the permissions for himself and his small partners, he finds that there are still errors in the landing production environment. The reality is that the classmate ignores the application pool identity account in IIS. In asp.net debug mode, the built-in Web server uses its own system account to access the database. Once the Web page is published to an IIS server, you also need to give access to the database to the application pool identity account that is configured in IIS. (And, of course, give the IIS Web site access to its own system login account)

In the second case:

The procedure execute permission used by the Drop-down list is not granted to the Access group. Syntax: GRANT EXECUTE on procedure_nm to public