July 3, 2023 at 2:22 pm
I have a problem where I intend the following on a Transactional Replication with a Push subscription;
1 - 10 rows were inserted into Table 1 on Publisher. I want these 10 rows to be replicated in Table 1 in the Subscriber. However, I want these data to reach the distributor but not the subscriber immediately. Only when I need them every 15 minutes.
2 - How do I stop the distributor from sending the data immediately to the subscriber?
Where do I schedule a job if necessary in order to stop the distributor from sending the?
Please start a new thread. This thread is 12 years old.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
July 3, 2023 at 2:23 pm
I have a problem where I intend the following on a Transactional Replication with a Push subscription;
1 - 10 rows were inserted into Table 1 on Publisher. I want these 10 rows to be replicated in Table 1 in the Subscriber. However, I want these data to reach the distributor but not the subscriber immediately. Only when I need them every 15 minutes.
2 - How do I stop the distributor from sending the data immediately to the subscriber?
Where do I schedule a job if necessary in order to stop the distributor from sending the?
Please start a new thread. This thread is 12 years old
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy