I have an issue where old transaction log files are not being deleted.
I have 4 publications, one is only executed when the client database
schema has changed, So it is only executed during application
upgrades. Looking at the dbmlsync log file i saw that for this
specific publication, the old transaction logfiles are scanned. An
entry must have been added to the log when the publication/
subscription was created when the database was used a first time by
the application. But there were no changes to the table that is used
in the publication.

Executing this publication randomly is out of the question...

What other options do i have?