Working within limits.
WHAT CONSTRAINS YOU
Limits on connections, queries and processes Shared memory and disk No access to server configuration Limits on database size or count
WHAT YOU CAN CONTROL
Your schema Your indexes Your queries How much data you keep
WHAT MATTERS MOST THERE
Indexing, since you cannot compensate with hardware.
WHAT COMMONLY CAUSES SUSPENSION
A query scanning a large table repeatedly An application looping queries Unbounded growth
WHAT TO DO IF WARNED ABOUT USAGE
Find the slow query, and index it.
HOW WITHOUT SERVER ACCESS
The application's own query log, or the panel's tools.
WHAT TO AVOID
Very large tables without indexes Storing files in the database Keeping every historical record indefinitely
WHAT TO USE FOR LARGE IMPORTS
The command line client, which handles what browser tools cannot.
WHAT TO DO ABOUT REGULAR REPORTING
Run it off-peak, or against exported data.
WHEN TO MOVE TO A DEDICATED SERVER
When the limits genuinely constrain a properly optimised application.
WHY THAT QUALIFICATION MATTERS
Moving an unoptimised application to a larger server postpones the problem.
