Note that there are some explanatory texts on larger screens.

plurals
  1. POAppHarbor Shared SQL Space Allocation Error
    primarykey
    data
    text
    <p>We are running the Shared SQL Server Addon under the 'Nano' Plan with 10GB storage.</p> <p>We are nowhere near approaching our storage limit yet we are intermittently encountering this SQL error when writing to the database:</p> <blockquote> <p>Could not allocate space for object 'dbo.<em>MyTable</em>' in database '<em>MyDatabaseId</em>' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.</p> </blockquote> <p>It seems the problem is because we do not have enough unused space at any given time for the tables we are writing to. Here is the output from <code>sp_spaceused</code> on each table:</p> <pre><code>name rows reserved data index_size unused ---------------- --------- ----------- ----------- ------------ ------ MyTable1 382862 177608 KB 177536 KB 8 KB 64 KB ---------------- --------- ----------- ----------- ------------ ------ MyTable2 137091 34248 KB 34240 KB 8 KB 0 KB ---------------- --------- ----------- ----------- ------------ ------ </code></pre> <p>EDIT: Further inspection shows the physical .mdf file has an Auto-Grow setting of 1024KB, should we expect to see a larger proportion of this as Unused table space?</p> <p>This is preventing us from creating indexes and worse still causing us to lose data. Is there a way to increase our allocation or another approach to take? Please advise.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload