tag:blogger.com,1999:blog-2173119910600284569.post4765973144098319050..comments2024-02-06T04:58:09.639-05:00Comments on Kendal Van Dyke: "Troubleshooting Transaction Replication" Published In SQL Server MagazineUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2173119910600284569.post-91982795495212861352010-06-24T08:27:32.881-04:002010-06-24T08:27:32.881-04:00Definitely a good article Kendall. Some great info...Definitely a good article Kendall. Some great information and always helpful to see other ways of approaching replication troubleshooting. :) <br /><br />Found the method you described for getting the failing command intriguing from the alert perspective and thinking about setting something up so that we can get that sent along with or following our alert. Should be interesting. Presently we strictly trace to get the failed commands as it seems quicker but that may not be true in all cases. <br /><br />Thanks again.David Benoitnoreply@blogger.comtag:blogger.com,1999:blog-2173119910600284569.post-51979907264489306942010-06-10T12:07:59.164-04:002010-06-10T12:07:59.164-04:00Kendal, I thought it was good, learned a few thing...Kendal, I thought it was good, learned a few things - the error skipping profile, the desktop memory thing. Things I'd add - Profiler is always valuable, as is viewing/logging output from agents, both are ways to understand 'is something happening'. Congrats on being published!Andy Warrenhttp://www.sqlandy.comnoreply@blogger.com