"Snapshot replication has a lower continuous overhead on the Publisher than transactional replication, because incremental changes are not tracked. "
In Snapshot replication it creates a snapshot at once and apply on the subscriber where as in Transaction replication the agent has to keep running on a certain regular interval to keep replicating the changes to subscriber.
Now obviously if you are running one service let's say for 20 minutes in a day and second service is keep on running after every 2 minutes(just example), the overhead of the second one would be much higher on publisher.
However, if the dataset set being replicated is very large, it will require substantial resources to generate and apply the snapshot.
Now lets come back to your scenario which is
see if your database is very large then obviously creating snapshot and replicating it to subscriber will also take many resources.
Consider the size of the entire data set and the frequency of changes to the data when evaluating whether to utilize snapshot replication. decision:
If your subscriber(s) can work on the data which is one day older obviously you can safely choose either snapshot replication or transactional replication.
If the database size is small you can also afford to create snapshot 3 or 4 times a day but if the size of your database is that big obviosly creating that much bulky snapshot and replicating it to all users would be not a good practice, Moreover if the database size is big we can safely assume that all the data is not changing everynow and then, comparatively a small portion of the data is changing so why to replicate the same bulky data again and again? instead we can use transactional replication the trade-of will be we can save a lot of resources in this case if we use transactional replication.
Sarabpreet Singh Sarabpreet.comSQLChamp.com