Yum, pickles… where was I?
Oh yea, SQL… I run a daily morning routine where I check error logs, mirror status and then replication status… What I find so odd is that this script runs fine for 6 weeks then this week it takes over 20 minutes to run the replication part. WTF? really SQL really? How come you run nice and smooth for 6 weeks and now it decieds to be an annoying little “B”.
Well I did a little digging and found that this “exec distribution.sys.sp_replmonitorhelppublication” little procedure runs a bunch of other scripts but if I go to the replication monitor it shows up almost instantly… so where the hell is it grabbing that data from?
I think we need to find out SQL’s secrets here and find out why this takes 20 minutes or longer to run and if there is any way to reduce this time… missing index? in inefficient cursor? or demon possessed server?
Any one have thoughts? Ideas? bread crumbs to lead us to the path?
Lets update this with ideas!