.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
david stephan

Home >> Interview Question >> ADO.Net >> Post New Question Subscribe to Interview Questions

Does ADO.NET supports automatic connection pooling?

Posted By :Virendra Dugar     Posted Date :November 11, 2009    Points :10   Category :ADO.Net 
Yes.

There is a pooling property with connection string. By default it is set to true.
Use this property to specify that a particular connection should not participate in the pool, but instead should be destroyed when it is closed.

You can also find related Interview Question to Does ADO.NET supports automatic connection pooling?  below: 

What is Connection Pooling ?

  
Connection Pooling will make a single connection instance, which allows that instance to connect to all the databases. Advantage is that it does not open and close the connection object multiple times. (More...)

What is Connection Pooling

  
Connection pooling is of

· A Connection Pool is a container of open and reusable connections. A Connection Pool is released from the memory when the last connection to the database is closed.

· The Data Providers in ADO.NET have Connection Pooling turned on by default; if you need to turn it off, specify Pooling = false in the connection string being used.

· Connection Pooling gives you an idle, open, reusable connection instead of opening a new one every time a connection request to the database is made. When the connection is closed or disposed, it is returned to the pool and remains idle until a request for a new connection comes in.

· The pool can house connections up to the maximum limit as specified in the connection string that was used to connect to the database.


(More...)

Parameters used in Connection pooling

  
Connection Pooling is controlled and the parameters passed to a connection string comprises the following:

· Connect Timeout

· Min Pool Size

· Max Pool Size

· Pooling

(More...)

Adv and Disadv of using Connection Pooling

  
Advantage of using Connection Pooling is an improvement of performance and scalability

Disadvantage is that one or more database connections, even if they are currently not used, are kept open
(More...)

What is Connection Pooling

  
Connection pooling is of

· A Connection Pool is a container of open and reusable connections. A Connection Pool is released from the memory when the last connection to the database is closed.

· The Data Providers in ADO.NET have Connection Pooling turned on by default; if you need to turn it off, specify Pooling = false in the connection string being used.

· Connection Pooling gives you an idle, open, reusable connection instead of opening a new one every time a connection request to the database is made. When the connection is closed or disposed, it is returned to the pool and remains idle until a request for a new connection comes in.

· The pool can house connections up to the maximum limit as specified in the connection string that was used to connect to the database.


(More...)

What are the Parameters used in Connection pooling

  
nnection Pooling is controlled and the parameters passed to a connection string comprises the following:

· Connect Timeout

· Min Pool Size

· Max Pool Size

· Pooling

(More...)

What are Advantages and Disadvantages of using Connection Pooling

  
Advantage of using Connection Pooling is an improvement of performance and scalability

Disadvantage is that one or more database connections, even if they are currently not used, are kept open
(More...)

What is a pre-requisite for connection pooling?

  
Multiple processes must agree that they will share the same connection, where every parameter is the same, including the security settings. (More...)

What is a pre-requisite for connection pooling?

  
Multiple processes must agree that they will share the same connection, where every parameter is the same, including the security settings. (More...)

What is connection pooling and what is the maximum Pool Size in ADO.NET Connection String?

  
A connection pool is created when a connection is opened the first time. The next time a connection is opened, the connection string is matched and if found exactly equal, the connection pooling would work.
Otherwise, a new connection is opened, and connection pooling won't be used.
Maximum pool size is the maximum number of connection objects to be pooled.
If the maximum pool size is reached, then the requests are queued until some connections are released back to the pool. It is therefore advisable to close the connection once done with it. (More...)

Explain in detail the fundamental of connection pooling?

  
ADO.NET with IIS uses a technique called connection pooling, which is very helpful in applications which regularly connecting to the database and accessing information on the server. In this if the database call is made for the first time the connection object is made, after release of connection that object is kept in pool and ADO.NET keeps reference to it. And next time when the request to execute any query/stored proc comes up, it bypasses the hefty process of establishing the connection and just picks up the connection from the connection pool and uses that for this database call. (More...)

Where do you store connection string?

  
Database connection string can be stored in the web config file.
The connection string can be stored in the WEB.Config file under
element. (More...)

What does connection string consist of?

  
The connection string consists of the following parts:
In general:

Server: Whether local or remote.

Uid: User Id (sa-in sql server)

Password: The required password to be filled-in here

Database: The database name. (More...)

What is Automatic Memory Management in ASP.NET?

  
Automatic Memory Management: From a programmer's perspective, this is probably the single biggest benefit of the .NET Framework. No, I'm not kidding. Every project I've worked on in my long career of DOS and Windows development has suffered at some point from memory management issues. Proper memory management is hard. Even very good programmers have difficulty with it. It's entirely too easy for a small mistake to cause a program to chew up memory and crash, sometimes bringing the operating system to a screeching halt in the process.

Programmers understand that they're responsible for releasing any memory that they allocate, but they're not very good at actually doing it. In addition, functions that allocate memory as a side effect abound in the Windows API and in the C runtime library. It's nearly impossible for a programmer to know all of the rules. Even when the programmer follows the rules, a small memory leak in a support library can cause big problems if called enough.

The .NET Framework solves the memory management problems by implementing a garbage collector that can keep track of allocated memory references and release the memory when it is no longer referenced. A large part of what makes this possible is the blazing speed of today's processors. When you're running a 2 GHz machine, it's easy to spare a few cycles for memory management. Not that the garbage collector takes a huge number of cycles--it's incredibly efficient.
The garbage collector isn't perfect and it doesn't solve the problem of mis-managing other scarce resources (file handles, for example), but it relieves programmers from having to worry about a huge source of bugs that trips almost everybody up in other programming environments.
On balance, automatic memory management is a huge win in almost every situation. (More...)

Quick Links For Interview Questions Categories:
ASP.Net Windows Application   .NET Framework   C#   VB.Net   ADO.Net  
Sql Server   SharePoint   Silverlight   OOPs   JQuery   JavaScript/VBScript
Biztalk Patten/Practices .IIS WCF WPF WWF
Networking Aptitude Others   All      

Find questions, FAQ's and their answers related to .NET, C#, Vb.Net, Sql Server and many more.

 
Now you can find lots of .NET, C#, Vb.Net, SQL Server,Windows, ASP.Net related Questions and their Answers here at www.dotnetspark.com. Our aim is to help you pass your certification Exams (MCP, MCSD, MCAD etc.,) with flying scores and get good name in your company.

So, Start looking our Interview Question section daily and improve your .NET Skills. You can also help others by posting Interview Questions and their Answers in this section.


Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend