Skip to main content
Question

Table becoming too full

  • October 4, 2023
  • 0 replies
  • 168 views

Hello,

I have a unique situation in that I have a table called TableA. TableA has many relationships and is rather intricate as it has a way to generate documents and such. This table also has many activity records, document records, etc. Unfortunately, the activities table mentioned above is at 90% capacity. 

What would be the best way to save/ archive the TableA records along with it's child records/ documents?

Looking for any and all suggestions or ideas

Thank you in advance



------------------------------
Shane Miller
------------------------------
    This topic has been closed for replies.

    MarkShnierYou
    Forum|alt.badge.img+24

    A low tech solution would be to copy your app and then have that app hold records prior to say Jan 1, 2022.  Go in to the Archive App any manually delete records more current than that.

    Then once you are doubly sure that you have records prior to that cut off date in your Archive App, go into your live app and delete records before Jan 1 2022. 

    Set access to the Archive app as View Only, and change the banner colour or App Home Page dashboard so Users easily know if they are in the Live app or the Archive App.



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------
    Mark Shnier. Your Quickbase Coach
    Forum|alt.badge.img+12
    • BrianSeymour
    • Registered
    • October 5, 2023

    Hey Shane,

    Unfortunately, that is not a unique situation and Quickbase has hard upper limits on some storage, so we are unable to "buy more horsepower." However, file attachments may be different, in that perhaps you can purchase more space? I'd open a Quickbase Support Ticket or review your contract (or Billing in the QB Admin Console) to confirm.

    In addition to what Mark suggested using Juiced Tech (which we've used with success in the past and would recommend), we also leveraged Pipelines to create Google Drive links to records and store files in Drive folders too, instead of native Quickbase.

    The place you're stuck now is migrating the existing file attachments from Quickbase to some third party, like AWS or Google, and ideally users wouldn't have to look in an archive prior to certain date. In other words, it may be nice to keep their workflow the same regardless of project age … Juiced should be able to help with the "sweep" functionality I imagine, otherwise you'd find a developer who can write a script to migrate your data.

    Also, to buy more time until you find a solution, I suggest checking the field properties of each of your three fields in Table "A." Scroll down to the "File Attachment field options" and review the value set in the "Keep the last (revisions)" which defaults to 3. If you don't need older versions, you may be able to set this to 1 and free up some space?



    ------------------------------
    Brian Seymour
    ------------------------------
    Terms & ConditionsAccessibility statement