Geek asks and answers

Maintaining one database connection or opening closure for every need

I am looking for best practice in the following case, with reasons why each method is better.

I have one database with approximately 10 ~ 20 client applications that connect to one main database server.

In very rare cases, there can be about 200 calls from one client to the database per minute.

The application is multi-threaded, about 20 threads for each application.

What will be best here is to support only one database connection for each application and reuse it for each application. OR open new connections for every call you need and quickly close them.

We work with oracle and sql server.

Thanks for your ideas.

+3
source share
3

.NET oracle . , , , . .

- using, , .

using(OracleConnection connection = ConnectionFactory.Create())
{
    connection.DoStuff();

} //connection.Dispose() called here.
+3

, . , .

SQL Server (ADO.NET)

MSDN:

, , . , using.

+1

, ( ) . - , POST . , - .

20 , 200 ? ?

, .

Are there some customers that are more important than others? If so, then you may need one client with 20 connections, and the rest with 10.

Any decent database setup should be able to handle several hundred connections and not fall if they all try to ping immediately.

0
source

More articles:


All Articles