Problem Summary: Why does the hvrpub (Transactional Replication – publication on <TestDB>) publication require the snapshot agent to run every hour?
This is creating GB’s of not used files. The log reader agent is used both by the HVR publication db and the publication team wants to setup.
This is logical as there can be only one log reader for the <TestDB> at a time.
HVR does need the hvrpub publication itself, but it does not need the Snapshot Agent to run. We do not need/use/create those agents.
The log reader agent is used both by the HVR publication db and the other publication team.
For co-existence with native replication you will need to set /LogTruncate to NATIVE_DBMS_AGENT, reinitialize and restart all capture jobs.
If you are using CAP_JOB_RETAIN, which most likely means that the database is running in Simple Recovery Model.
Co-existence scenario (using HVR and Native replication at the same time) is not possible in this case.
This a fundamental limitation. For coexistence the database needs to be in Full recovery mode.