Does anyone know much about SQL Replication (SQL Server 2005)

Man of Honour
Joined
18 Oct 2002
Posts
13,262
Location
Northallerton/Harrogate
I'm trying to follow some tutorials on MSDN and I'm failing.
Publishing Data Using Transactional Replication....
(http://msdn.microsoft.com/en-us/library/aa337453.aspx)

I've got most of the way through this one.
I've set up all the windows accounts for replication and configured distribution (afaik)

However when I get to step ... well the last part of Lesson 2 (Creating a Subscription to the Transactional Publication) it says:
To view the synchronization status of the subscription
Connect to the Publisher in SQL Server Management Studio, expand the server node, and then expand the Replication folder.

In the Local Publications folder, expand the AdvWorksProductTrans publication, right-click the subscription in the ProductReplica database, and then click View Synchronization Status.

The current synchronization status of the subscription is displayed.

If the subscription is not visible under AdvWorksProductTrans, press F5 to refresh the list.


However, I get (for the status):
The concurrent snapshot for publication 'AdvWorksProductTrans' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for ....I'm sure there should be more here.

My question is this:
How do I start this Log Reader Agent if it needs to be running? http://msdn.microsoft.com/en-us/library/ms146878(SQL.90).aspx - all foreign to me. Should I have run some form of that command? I'm not sure (haven't a clue) what to do with the information contained on that page.

Also - My subscriber and publisher is the same machine (different database) - is that ok, or am I retarded?
There's nothing been said in this tutorial about you have to connect from another machine running SQL server on it (for the subscriber)...so I haven't been.

Totally new to this lark and I'm lost.

Thanks,
J.
 
Sooo - I've discovered I need to run logread.exe from a command window
It's the parameters I'm not so sure about..I'll have a play but assume I'm still stuck.
 
Thing is, I'm not sure what the solution was exactly....(otherwise I would have).

That agent should've started itself automatically and not from the command line - but I think the problem was that I'd screwed up somewhere along the way and created extra jobs for SQL to do, and then when I tried another way (using the same user/database names) but trying a different replication method it fell over when jobs conflicted with one another, but had to dig for the actual reasons.

Solution: Disable replication, delete all database/publication/subscription/job/etc that had been created, leaving only the sample database on my server. Oh, and I kept the windows user accounts I'd created too...

Go through the distribution wizard again, then the publication wizard/subscription wizard etc... and my log reader agent decided it wanted to run (must've been the job conflict) and hooray, working replication.

this link was some help...recommended disabling replication and starting over. Although some replication data wasn't automatically dropped/deleted - had to manually kill some of those things.

Now I just need to test it with multiple remote subscribers.
 
Back
Top Bottom