Aspdotnet-Suresh

aspdotnet-suresh offers C#.net articles and tutorials,csharp dot net,asp.net articles and tutorials,VB.NET Articles,Gridview articles,code examples of asp.net 2.0 /3.5,AJAX,SQL Server Articles,examples of .net technologies

C# - Adding the Specified Count to the Semaphore would Cause it to Exceed its Maximum Count in SQL Server / Asp.net

Jul 9, 2013
Introduction:

Here I will explain how to solve the problem “adding the specified count to the semaphore would cause it to exceed its maximum count in c# / Asp.net / sql server .” When running asp.net web application in c#, vb.net with SQL Server database.

Description:


In previous posts I explained many articles relating to solve errors in asp.net, SQL Server, IIS, etc. Now I will explain how to solve the problem of “adding the specified count to the semaphore would cause it to exceed its maximum count in sql server”. To solve this problem we need to add “Pooling=False” in database connection string to disable connection pool in web.config.

Default Connection String

<connectionStrings>
<add name="dbconnection" connectionString="Data Source=SureshDasari; Initial Catalog=TestDatabase; Persist Security Info=True;User ID=test;Password=test;" />
</connectionStrings>
After Adding Pooling in Connection String

<connectionStrings>
<add name="dbconnection" connectionString="Data Source=SureshDasari; Initial Catalog=TestDatabase; Persist Security Info=True;User ID=test;Password=test; Pooling=False;" />
</connectionStrings>
Once we add “Pooling=False” condition to connection string then it will disable connection pool and run application without any problem. To know more about connection pooling check this article Connection Pooling

Happy Coding………                                                   

If you enjoyed this post, please support the blog below. It's FREE!

Get the latest Asp.net, C#.net, VB.NET, jQuery, Plugins & Code Snippets for FREE by subscribing to our Facebook, Twitter, RSS feed, or by email.

subscribe by rss Subscribe by RSS subscribe by email Subscribe by Email

8 comments :

Dhiraj said...

good one ....

Irtekaz Ahmed Khan said...

ok sir,

Anonymous said...

Hey this is very nice.....................

C# .Net Code said...

thnx yar....

Unknown said...

thank u..............................

Anonymous said...

Excellent post. Microsoft need to learn from you for a quick and simple way to solve issues like this.
Chris

Anonymous said...

Thank you.......

Anonymous said...

Worthless answer. Connection pooling is there to solve performance issues.

Give your Valuable Comments

Note: Only a member of this blog may post a comment.

© 2015 Aspdotnet-Suresh.com. All Rights Reserved.
The content is copyrighted to Suresh Dasari and may not be reproduced on other websites without permission from the owner.