Skip to main content
Ester.Memoli
Ester.Memoli
Helper ⭐️
Sep 15, 2022 3:09 PM UTC
Solved

Low Volume object with more than 1 million records

Hi,

I created a low volume custom object, but during the imports we added more and more data, and now it contains 1.8M records.

 

As the maximum should be 1M, what should I expect from it? Which problems may happen?

Really curious. :D

 

Thanks

    pope1chase
    pope1chaseAnswer
    Helper ⭐️
    Nov 1, 2022 8:15 PM UTC

    I haven’t found any documentation specifically related to the pitfalls of adding more than 1M records for low volume custom objects. From a generic database perspective, I would expect to see slower system performance, updates taking longer to display, and even possible data corruption through APIs.

    View in thread

    2 replies

    pope1chase
    pope1chaseAnswer
    Helper ⭐️
    Nov 1, 2022 8:15 PM UTC

    I haven’t found any documentation specifically related to the pitfalls of adding more than 1M records for low volume custom objects. From a generic database perspective, I would expect to see slower system performance, updates taking longer to display, and even possible data corruption through APIs.

    Translate
    Ester.Memoli
    Ester.MemoliAuthor
    Helper ⭐️
    Nov 25, 2022 2:26 PM UTC

    I haven’t found any documentation specifically related to the pitfalls of adding more than 1M records for low volume custom objects. From a generic database perspective, I would expect to see slower system performance, updates taking longer to display, and even possible data corruption through APIs.

    Hi @pope1chase it is indeed what Support told me.

    I can say that even with 3 M records I didn’t see any performance reduction, but I nonetheless decided to switch to a ahigh volume object.

    Translate
      Terms & ConditionsAccessibility statement