MCAD question on Configuration Manager and connection pooling
-
Trying to get thru a MCAD question, hope you can help me out on this: You're creating an ASP.NET application. The application will be deployed on XXX's intranet. XXX uses M$ Windows Authentication. More than 150 users will use the ASP.NET application simultaneously. The project manager wants you to use connection pooling. What should you do? a. Add following element to the authentication section of the web.config file: b. Use the configuration Manager for your project to designate the user's security context. c. Write code in the Application_AUthenticateRequest event handler to configure the application to run in the user's security context. d. Add the following element to the system.web section of the web.config file: The model answer is B. But what the hack is "Configuration Manager". Where can I access it, what does it do and what does it has to do with connection pooling? Thanks.
-
Trying to get thru a MCAD question, hope you can help me out on this: You're creating an ASP.NET application. The application will be deployed on XXX's intranet. XXX uses M$ Windows Authentication. More than 150 users will use the ASP.NET application simultaneously. The project manager wants you to use connection pooling. What should you do? a. Add following element to the authentication section of the web.config file: b. Use the configuration Manager for your project to designate the user's security context. c. Write code in the Application_AUthenticateRequest event handler to configure the application to run in the user's security context. d. Add the following element to the system.web section of the web.config file: The model answer is B. But what the hack is "Configuration Manager". Where can I access it, what does it do and what does it has to do with connection pooling? Thanks.
First, I'm not sure either what they mean by "Configuration Manager". However, as I recall, for connection pooling to work all connections must use the same connection string. So if all the users are connecting like this: "Server=MySQLBox;Database=MyDB;Userid=someusername;password=somepassword" then connections won't be shared. However if all the users connect through the same account, or a trusted connection, then the connection string will be the same each time. My guess would be that as it is an intranet application and MS Windows Authentication is available the Trusted Connection route is the correct one. So each windows user (or better role) that should get access needs to be set up in SQL Server (This can be done in SQL Server 2000 Enterprise Manager) --Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)