I just want to know is there attribute or property in our connectionstring field so that we can maintain an optimized db connections with our clients. Like in general I use.That contains just required info.
<add name ="ConnectionString" connectionString="Data Source=118.225.221.7;Initial Catalog=mycatalogue;
User Id=dba; password=some_password"/>
Another Scenario, we can enhance our connection string for MARS and Asynchronous operations too:
MARS
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;
MultipleActiveResultSets=true;
Asynchronous Processing
Server=myServerAddress;Database=myDataBase;Integrated Security=True;
Asynchronous Processing=True;
From our pages i have 4-5 or sometimes ~10 connections to access data. Take a case when I have 100 users accessing the same page simultaneously assuming the code is executing "SELECT"
statement and fetching some random rows for each client. Then 400-500 connections will hit the db at a time, which I think, will definitely degrade the server/application performance.
So I want to know, should I minimize the number of queries, or leave it to the .Net framework intelligence.