302 Found

Found

The document has moved here.

Knowledge Base

Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.

How can I manage my application's tables?

Table size can significantly affect QuickBase performance, including the speed with which QuickBase searches tables and runs reports.   We recommend that you schedule regular reviews of your applications to see how much storage space each table is using and whether you can tweak your tables to optimize performance. For tables that are using a large amount of storage space, consider reducing table size by moving data either up into a master table or down into a detail table, or by removing unused fields.  In some situations, you may find it useful to institute a strategy for archiving older records. 

Note:  Consider documenting the structure of your application so that you have a record of each table’s and field’s purpose that you can use when reviewing your application. You can create an Application Page with this information, or use one of the tools created by our QuickBase partners.

Monitoring Storage Space Usage

To see how much storage space each table is using, select Customize > Application from the menu bar and click the Misc tab.  Click the Show Application Statistics link.

Show Application Statistics

If you are the billing account manager, you can also see how much storage space each table is using by clicking the Manage my billing account link on the My QuickBase page and selecting an application on the Applications tab.

Note: Although the Application Statistics page shows you the amount of attached file space used by each table, file attachments count towards your billing account limits, not your table size limits.  Like all fields, file attachment fields themselves take up table space, but the uploaded files do not. Deleting file attachments will not decrease your table size. (If you notice you are getting close to your billing account’s attached file space limit, you can use the File Attachment Management page to identify large files and to delete unused file revisions. Read more about managing file attachments.)

Optimizing Application Performance

When reviewing your tables to optimize performance, consider the following points:

  • If you have a large table that serves many functions, consider breaking the table into multiple, related tables. You then can leverage lookup fields, formula fields, summary fields and report link fields to run reports containing data from the related tables.  These fields do not affect table size. Read more about converting a field into a table and creating relationships.

  • Large tables can result in many unused and dormant fields.  Unused fields still occupy storage space. (Read more about how much space is used by each field type.)  To help identify fields in use, compare the list of fields in the table to the fields that appear on the table’s current forms. If your table contains fields that are not used on any forms, or that are empty in a majority of records, those fields may not be necessary for your application. 

  • Review your table’s records for repeat data.  Repeated data can be ‘normalized’ by creating a separate master table that stores this data once, and references it in details records as many times as you like with no storage impact. For example, if your Contacts table repeats the same town, state, and zip code in many records, you could create a table to store town information and create a relationship to the Contact table.

  • Look for logical ways to segment in your data, such as by years.  You can create separate tables for each of the last few years and export that data into their respective years (2009, 2010, 2011, etc.).  This option has the benefit keeping your data active and close while dramatically reducing the storage space used by table.

  • Wherever possible, consider how you can leverage lookup fields, formula fields, summary fields and report link fields.  These fields do not affect table size and enable you to run reports containing data from multiple tables.

  • If your table contains large multiple-choice dropdown fields, consider converting these fields to a master table. This not only saves table space but it also reduces your overall application storage space.

  • If your table contains multi-line text fields that are set to append only, consider converting those fields to detail tables.  The data is still displayed in embedded reports for the master table, but the master table uses less storage space. 

Archiving Data

If you are interested in archiving your data, you can:

For Additional Help

Please submit a support case if you would like help determining the best strategy for managing your applications.  You can enter a support case from any application page by selecting Help > Support and clicking the Contact Support button.

Our support team also can help match you with a QuickBase partner specializing in application development and performance tuning.

Comments

Application Table is full

To Whom it may concern:

I am attempting to enter in DRA's for Shell Chemical in Deer Park, TX.

The message I am getting after entering in my DRA's is that my application table size limit has been reached and it is not saving the data I have entered.  Please can someone assist me in getting this problem resolved.

Thank you,
Zach Ballew

contact the billing account manager...

Hi Zach --

I apologize for the delay in answering your question. The message you are seeing should be reported to your company's QuickBase billing account manager. If you don't know who that is, asking your application's administrator may prove useful. The billing account manager should contact QuickBase billing to resolve the issue, if he or she has not already done so.

Regards,

--Sybil

Post new comment

The content of this field is kept private and will not be shown publicly.
Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.
302 Found

Found

The document has moved here.