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 8847531
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T12:12:43+00:00 2026-06-14T12:12:43+00:00

When issuing a MySQL/SQL query from PHP code, a connection with the database must

  • 0

When issuing a MySQL/SQL query from PHP code, a connection with the database must be firstly established.

Would you advise me, please, whether I should establish connection with the database only at the beginning of the user’s web session, or upon loading new page, or before every single MySQL/SQL query?

I think that when establishing connection with the database too many times unnecessarily, I will consume unnecessary system resources. I would therefore prefer connecting with the database the minimum necessary times.

  • 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-06-14T12:12:44+00:00Added an answer on June 14, 2026 at 12:12 pm

    You need to strike the right balance. Each part has its problems. Let’s go over all three possibilities

    Persistent MySQL connection

    Advantages: load-once-and-forget

    Disadvantages: you’ll need to make sure to kill any connection that is not active anymore yourself. Also, a dormant connection still uses some resources. Not recommended, as the only good case for it is a lot of requests, at which point you’ll most likely want to cluster up your database servers, and persistent connections tend to play havoc with that.

    One-query-one-request model

    Advantages: build-and-forget

    Disadvantages: extreme resource usage.

    The good solution is a right balance. Load up your DBH when you actually need it for the first time, and keep it until your script is over, at which point you should free all resources used by it and terminate it. This guarantees that you’ll have done everything using the minimum amount of resources needed.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Issuing the following query: SELECT t.seq, t.buddyId, t.mode, t.type, t.dtCreated FROM MIM t WHERE
Would be possible to check if an association exists before issuing a query in
When issuing a query against a database, at what depth of an object graph
The following code is issuing the following error message: A Database Error Occurred Error
MySQL is issuing this error when I try to execute a query where the
I am issuing a query to elasticsearch and I am getting multiple record types.
I have a simple entity, Code, that I need to persist to a MySQL
I have this real weird exception when issuing a basic SELECT, using MySQL 5.1.32-community
I am issuing many parallel robocopy calls to copy files from one network share
I'm looking for a way to prevent multiple hosts from issuing simultaneous commands to

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.