How large of a database can Triggre handle?

Hi everyone,

I have a question concerning the limitations of the database size of a Triggre application. We want to build an application with which we can GET information from different other applications (multiple ERP/administrative applications).

This information needs to land in Triggre so we can do calculations or other mutations with it. With the data in Triggre we want to create rapports of the data (our own merged tables - with data from different apps) or we want to provide different BI opportunities (or send it to Power BI).

You could imagine that we need quite a lot of tables for this application, especially when the amount of applications that we want to fetch data from are increasing.

We currently started with one application, and we already notice that our DB structure is becoming quite big. I am wondering how others perceive this, and maybe if we can do something about this to maintain a certain level of overview.

All ideas are welcome, thanks in advance!

Hi Thijs,

Great to hear that your application is growing!

In terms of the size of the database, Triggre can handle a lot. We have customers who have hundreds of millions of records and some database tables alone containing many Gigabytes of data.

Some of these customers have exactly the setup you refer to, with data coming in from multiple other applications.

Hope this helps!


Hi Jesse,

Thanks for the explanation. Good to know that the Triggre database can handle a lot of entries.

The question I was more concerned about however is the amount of tables, and their connection. We work with a canvas like interface, which at a certain point has its limitations.

I am looking for the right way to organize/structure my database on this canvas so that I maintain a good overview of all the tables and their relations.

Any tips/advice or even examples are welcome. Thanks in advance!

Hi @thijs,

That is a different matter indeed. What we do ourselves is placing the data items grouped together when they are related to similar functionality.

An alternative is to use prefixes, for example USR Statistics for User statistics or something along those lines. This is especially helpful combined with the next tip :smile:

Lastly, there is a search function (either click the little magnifying glass or just start typing) that will turn the canvas view into a list of results.

Hope this provides some help.

1 Like

This definitly helps, thanks Jesse!

1 Like