September 20, 2011 at 1:06 pm
Hey all,
I am in charge of maintaining and troubleshooting replication for several clients using SQL 2008 and SQL 2000. One thing that's been frustrating me for a while is that it seems that SQL 2000 is much better about reporting errors than SQL 2008.
SQL 2000 will put X's right through to the top of replication monitor if something goes wrong. SQL 2008 seems to say everything's fine almost all the time. The one indicator I see of problems is the subscription performance getting decreased if there is a problem.
I'm troubleshooting replication at a client, and I'm just at a loss as to what to do. I've checked the agent profiles, but everything seems fine, and yet in a 3 server setup, 1 server isn't replicating to the others. I realize that I haven't provided enough info to ask about the specific case, but what I'm really wondering is: Does anyone have any suggestions on how to effectively troubleshoot replication on SQL 2008? Ideally, I'd want some way that would yield some verbose logs. I'd appreciate any advice anyone can give. Thanks.
September 20, 2011 at 2:57 pm
did you start up the replication monitor
September 20, 2011 at 3:36 pm
Some articles that might help you:
http://blogs.msdn.com/b/chrissk/archive/2009/05/25/transactional-replication-conversations.aspx
Setting up verbose logging -> http://blogs.msdn.com/b/chrissk/archive/2010/01/05/walk-through-of-kb-article-312292-how-to-enable-replication-agents-for-logging-to-output-files-in-sql-server.aspx
September 20, 2011 at 3:44 pm
danschl (9/20/2011)
did you start up the replication monitor
Yeah, I started that. That's the thing that in SQL 2008 I find a little too optimistic and worry-free.:-)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply