Question

My application is on ASP.NET 4 with SQL Server 2008 R2 backend.

Connection string is using Integrated Security. I want to know what are the advantages of adding:

pooling = true;
max pool size = N

in the connection string when Integrated Security is set to true.

Shall I enable it or not?

Edited

Is the problem discussed in this question possible when pooling is not enabled?

Application starts displaying wrong data but corrects when SQL Server service restarts.

Edited:

The Web.Config file contains following lines:

<add name="ConStringPWS" connectionString="Data Source=.;Initial Catalog=pWS;Integrated Security=True;" providerName="System.Data.SqlClient"/>

<identity impersonate="true" userName="Server\Administrator" password="xyz"/>

Answer 1

Yes, i think we should enable the connection pool.
(Actually, by default the pooling is enabled and max pool size is 100)

As far as i know, The pooling is not related to Integrated Security configuration.

Pooling connections will help your application on better performance and better scalability area. Pooling is a technique to reduce the cost of repeatedly opening and closing connections(Physical).

As far as i know to answer your question, How to check Pooling is enable or not.
I think someone here can give you a better answer.

SqlConnectionStringBuilder cnnBuilder = new SqlConnectionStringBuilder(yourConnection.ConnectionString);
bool isPooling = cnnBuilder.Pooling;