Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3333040
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T23:45:10+00:00 2026-05-17T23:45:10+00:00

If connecting to a database consumes a lot of resources, why should a database

  • 0

If connecting to a database consumes a lot of resources, why should a database connection always be closed in your application if you have to open it again? Can I just make this connection available globally throughout my application so that other classes and methods can reuse it?

For example (in pseudo code):

public class PopulateGridViews()
{
    public SqlConnection conn = new SqlConnection(@"Database:DATABASE");
    conn.Open();

    void PopulateGrid1()
    {
        SqlCommand cmd = new SqlCommand("SELECT * FROM TABLE1");
        cmd.Connection = conn;
        cmd.ExecuteNonQuery();
        cmd.Dispose();
        // Populate Grid1
    }

    void PopulateGrid2()
    {
        SqlCommand cmd = new SqlCommand("SELECT * FROM TABLE2");
        cmd.Connection = conn;
        cmd.ExecuteNonQuery();
        cmd.Dispose();
        // Populate Grid2
    }
}
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T23:45:10+00:00Added an answer on May 17, 2026 at 11:45 pm

    You should not leave connections open.

    You should:

    1. Open connections as late as possible
    2. Close connections as soon as possible

    The connection itself is returned to the connection pool. Connections are a limited and relatively expensive resource. Any new connection you establish that has exactly the same connection string will be able to reuse the connection from the pool.

    We strongly recommend that you always
    close the connection when you are
    finished using it so that the
    connection will be returned to the
    pool. You can do this using either the
    Close or Dispose methods of the
    Connection object, or by opening all
    connections inside a using statement
    in C#, or a Using statement in Visual
    Basic. Connections that are not
    explicitly closed might not be added
    or returned to the pool. For more
    information, see using Statement (C#
    Reference) or How to: Dispose of a
    System Resource for Visual Basic. Ref.

    You should appropriately wrap anything that implements IDisposable in a using statement block:

     using (SqlConnection connection = new SqlConnection(connectionString))
     {
         connection.Open();
    
         ...
    
         command.ExecuteNonQuery();
     }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am connecting a MYSQL database through hibernate and i seem to have processes
I have a method which is connecting to a database via Odbc. The stored
I am connecting to a DB2 database (DB2 v9.7.400.501) from my Java web application
I have a front-end Access 2007 database connecting to MySql tables using MySQL ODBC
I have a java application where on thread is the socket connection which captures
I'd like to have a function behaving as mysql_real_escape_string without connecting to database as
At the moment I have a website that is connecting to the database the
Whenever I call my logger in a method, e.g. _logger.Debug(Connecting to database...); I get
I'm connecting to a database server (MSSS 2005, 9.0 SP2) which is almost totally
I've got problem with connecting to MySQL database on my freshly installed Windows 7

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.