What is the recommended number of records to create in a table?

[bonsai]

I would like to change the deletion of records in the "sysevent" table from 7 days.

This seems to be done using the Table Rotation Group and Auto Flushes functions.

If the retention period is extended from 1 week to 35 days, a large amount of data will be stored in the table.

Will there be any performance impact due to the large amount of data?

[Fabian Kunzke]

Hey,

If there is no "real" reason for this change, i would advise against it. Large tables will reduce the performance for data querying. The sysevent table is one of the core tables for flows & event queueing. If this table contains larger amount of data than it already does it may slow down workflow & event driven actions.

This is a maybe.

At the end of the day increasing any amount of data by that much, a negative impact to data interactions on said table will happen. If that impact is noticeable, is a question i cannot answer. However, i wouldn't take a risk on a core table like that.

Regards

Fabian

[bonsai]

Thank you for your answer.

My goal is to keep logs for more than 7 days in order to investigate when a problem occurs.

I would like one month if possible...

I feel like there is less risk in increasing the number of tables to rotate, but what are your thoughts on this?

I think I'll end up asking support about it...

[Fabian Kunzke · Accepted solution]

I'd recommend to check with support. They will be in the best position to also give a clear answer in regards to performance impact - as this is always somewhat related to each instances specifics.

[blaze1]

If you increase the retention period for records in the sysevent table from 7 to 35 days, more data will accumulate. This can lead to:

1. More storage use: The table will take up more space.
2. Slower queries: Searching or reporting on the table might slow down due to the larger amount of data.

Ways to manage:

• Table Rotation: Moves old data to another table to keep the main table small.
• Auto Flush: Automatically deletes records after a set period, like 35 days, to manage data size.

Recommendations:

1. Archiving: Move older records to a different table if you don’t need them often.
2. Indexing: Make sure the table is indexed properly to speed up searches.
3. Monitor performance: Keep an eye on query speed and disk space as the table grows.

In summary, while storing data for longer can give you more records, it may affect performance, so managing how and when data is deleted or archived is important.