SQL Server Replication - only ran once. How to configure scheduler from beginning

Question

I have configured a transactional replication from server A to Server B some 2 month ago. The source database is a new production server, and the data is being updated there constantly. I have some issues ... I am not sure how to resolve.

1. I see that the "last sync" occurred 2 month ago, when I initially set it up.
   • I was expecting a snapshot job to be of a periodic nature, but it is not.
   • It is actually set to a "One time" and is not enabled. I know, I can "enable it" and set the schedule for the future, however I am looking for how to do it at the time when I configure the replication. I may be configuring it with the script and be expecing the configuration go into effect from the power shell script rn, and want to make sure i know how to set the schedule from the beginning.

This is what I see in a schedule of a Snapshot job on the Sql Server agent.

Answer 1

I think there is a misunderstanding how transactional replication works. From documentation:

Transactional replication typically starts with a snapshot of the publication database objects and data. As soon as the initial snapshot is taken, subsequent data changes and schema modifications made at the Publisher are usually delivered to the Subscriber as they occur (in near real time).

So basically an initial snapshot is created and afterwards transaction log is scanned for any subsequent changes. Unless something breaks horribly or there is a need to add another subscriber ( and the initial snapshot expired), there is no need for additional snapshots. But even if that is the case, there is no need to fiddle with the agent job directly. I always did things similar to described in tutorial

It may be there is actually another problem as hinted by comment under the question. In this case new question would be appropiate in my opinion.