Link to home
Start Free TrialLog in
Avatar of rzup
rzup

asked on

SQL Sever Replication - is there a good place to check the state of the data in large replications?

I have a SQL Server 2005 (std) database that replicates across a relatively slow link (DS1) to another server (same type)--I replicate an entire database (not just a few tables). Recently I had to delete and start the replication again, since it is 70gigs in size, it takes a long while to replicate. I notice after a day, it has created the schema on the subscriber, but no data is present in the subscriber (I started by deleting the old subscriber db and starting with just the db and no schema or data).  The job seems to still be churning. Is there a way to see where it is or view the data? I feel like it's too much in the background and I can't tell the state of the replication or if it will be ultimately successful.  

Any good tools for monitoring replication more granularly--I'd like to know exactly what is it doing at the moment. This is a pull-based replication created using the replicaiton options in 2005 (built with management studio)
ASKER CERTIFIED SOLUTION
Avatar of lcohan
lcohan
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of rzup
rzup

ASKER


The replication monitor looks like a pretty good tool, thanks.

I am looking at the replication monitor. it says the Log reader agent is running, but it shows "no replicated transactions are available".  Why would that be? Under the undistributed commands there seem to be 1302 commands ready waiting to be applied. I'm really still not sure if anything is happening--it looks like not. Even though the data is clearly not synchronized. Thanks for the suggestions.
Avatar of rzup

ASKER

Looks like the replication monitor is finally showing some signs of activity in the  associated logs. Thanks for the pointer