| Author |
Topic |
|
betesh
Starting Member
34 Posts |
 Posted - 2008-06-22 : 08:41:35
|
| Hi Everyone,I am towards the end of setting up transactional replication but I am getting stuck.I don't know if I am going about this in the right way but here is what I did:- Setup Distributor- Setup Publisher for Transactional Replication with updatable subs.- Setup Subscriber with PULL Subscription- Updated a record on SubscriberNow I am getting stuck with setting up a job with SQL Server Agent. What do I do to get it to synchronize the changes? I tried a few different kinds of steps (e.g. Replication Distributor) but got errors. I have researched online and can't find anywhere a detailed description of how to set up the job to effect synchronization.What am I missing? |
|
|
sachinsamuel
Constraint Violating Yak Guru
383 Posts |
Posted - 2008-06-22 : 12:15:50
|
| Whats the error you encountering in the job?Don't sit back because of failure. It will come back to check if you still available. -- Binu |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-06-22 : 12:41:11
|
| Did you check in Replication monitor or Agent status? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-06-22 : 17:03:20
|
| Once you configed replication properly, sql agent will start torun those jobs. |
|
|
|
betesh
Starting Member
34 Posts |
Posted - 2008-06-23 : 02:10:44
|
| Thank you all for replying. I don't recall seeing a specific error message but I am going to check now if the replication ever happened. Again, I appreciate everyone's input. |
|
|
|
betesh
Starting Member
34 Posts |
Posted - 2008-06-24 : 02:03:35
|
| I still don't understand how it is supposed to work. After I make the change in the subscriber database, then what? I create a job? What kind? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-06-24 : 02:09:05
|
| You don't make the changes in the subscriber database. You make the changes at the publisher. It goes from publisher to subscriber. You don't create any jobs, replication wizard takes care of all of that.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
betesh
Starting Member
34 Posts |
Posted - 2008-06-24 : 07:43:56
|
| Hi Tara,Thank you for responding. - I am doing two-way replication (transactional with updatable subscriptions). It needs to be pull subscriptions as the subscribers use VPN to get to the database server. Does that address the first point you made?- When I create a subscription that runs continuously then yes, all the updates happen automatically. But when I want the syncronization to be manual, or scheduled to run daily, that is when it isn't working for me at all. Since these users are on VPN, the whole point is that they can work locally and then once a day sync up with the main database, instead of continuously.Does that make sense?I don't know why in the world I can't get the on-demand subscriptions initialized and setting up a job for synchronization. |
|
|
|
betesh
Starting Member
34 Posts |
Posted - 2008-06-24 : 08:02:50
|
| As an update now I am testing replication on 2 databases on the same server. I wanted to see if I could get the manual synchronization working without the remote factor as a start.I did "View Synchronization Status" and started it. It worked but what happened was the publisher overwrote the subscriber. Is that because it just put a snapshot in instead of checking for differences? To clarify there is a field that I updated in the subscriber from NULL to a value. After the sync the field went back to null as it is in the publisher. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-06-24 : 11:14:34
|
| It doesn't matter if it's pull or push. You still need to update the publisher instead of the subscriber. The publisher is the parent of this process. So reverse your setup.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
betesh
Starting Member
34 Posts |
Posted - 2008-06-24 : 15:20:15
|
| But when I look in the publisher I don't see anywhere that it knows about the subscriber. Where specifically can I see that the server knows about the subscriber?Can you be more specific please? I would really appreciate it as I find the Books online are good at explaining concepts but not how tos. That is my problem - how to set up synchronization for pull subscription. I think we are narrowing in on it but still haven't gotten to actually explaining how to do it. Which jobs do I need or what else do I need to do? I am relying on this forum as I find you all responsive and willing to help and have very limited other resources if any - thanks again!!! |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-06-24 : 15:23:54
|
| When you setup replication, you specify who is the publisher and then who is the subscriber. You've set it up in the reverse. Delete the subscription and then the publication. Now set it up again now that you know the publisher is the parent.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
betesh
Starting Member
34 Posts |
Posted - 2008-06-26 : 03:46:39
|
| It is pretty hard to debug other people's problems over the internet, but no, that wasn't the problem. The problem was that I was trying to set up a pull subscription on the client with Express edition through the wizard which didn't work.Now I am using the SP's to set up replication. This works, however I still have an issue setting up a shared folder so the snapshot taken at the server can be seen by the client to initialize the subscription.If anyone ever comes accross this thread and wonders what answer I was seeking that took me so long to find here it is:http://msdn.microsoft.com/en-us/library/ms165686.aspxIf anyone has any tips on setting up the shared folder or network drive that would be welcome as well. We connect to the server via VPN. |
|
|
|
|
SQL Agent Job Fails