Best approach to handle large Serilog MSSQL log tables (indexing issues)

[marrale]

Hi,
I have a C# service running on two nodes that both write concurrently logs to the same database table using the Serilog MSSQL sink. The log retention period is 60 days. After some time, it becomes impossible to index the log table through the optimization script.

Here are my current Serilog MSSQL sink settings:

sinkOpts.AutoCreateSqlTable = true;
sinkOpts.BatchPostingLimit = 100;
sinkOpts.BatchPeriod = TimeSpan.FromSeconds(5);

What would be the best approach to improve?

• Move log entries to an archive table after a certain number of days (or even minutes)
• Adjust the Serilog MSSQL sink options, for example deactivating "AutoCreateSqlTable"
• Any other suggestions?

Thanks and BR ale