Home/ Questions/Q 6746345
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T12:18:41+00:00

I’d like to know the most common mistakes a developer can make that may

  • 0

I’d like to know the most common mistakes a developer can make that may cause a Database Server to crash and/or become unresponsive and/or abort.

I’ve had this problem some times now and I’d like to know what are some common mistakes that(mostly unexperienced) developers who write the queries and the scripts that access the database server can run into.

I’m not really looking at things from a DBA’s perspective, am rather hoping I can have a simple list with perhaps some ‘good practices’ for developers who have to work with databases on a daily basis (like me).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Main reason I see crashes / hangs, in order from most frequent to least frequent:

    1. A frequently used query having a ludicrous number of JOINs, or returning a massive amount of data.
    2. Very IO intensive queries, such as a LOAD DATA INFILE on MySQL.
    3. Heavy use of table locks that cause a massive backlog.
    4. Machine ran out of memory and the DBMS process was killed to prevent the whole box crashing.
    5. Some client code spazzing out and flooding the DBMS with too many connections, causing legitimate client connections to time out.
    6. The DBMS crashing due to a bug. Rare, but annoying to track down.
    • 0