March 4, 2011 at 11:15 am
Definitely seems odd. Is that the only publication for that database? Assuming yes. The only other thing that I could say you could do is to remove the publication again, and set the database to not be published. Then enable publication again and add publication, subscriptions to see if that works.
We could try to delete the commands but if you are able to rebuild it again then this will be cleaner.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 4, 2011 at 11:29 am
There is an additional snapshot publication that runs twice daily but that's wokring just fine.
I have 3 databases replicating (each with about 30 tables), each having 1-2 snapshot replication runing in addition to the transactional replication. Everything is working fine except the transactional replication for database A, which I had to restore last night in a DR situation.
I don't understand why deleting the publication from the publisher and subscription from the distributor and then regen everything like it was the first time didn't fix it up...unless it's because there's stuff lingering around in the distribution db.
If I disabled the distributor and everything else, deleting everything from all locations and started over, that would be like starting from scratch right?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 4, 2011 at 12:00 pm
I would agree that it is remnants in the distribution database. I would NOT disable the distributor just disable that database from being a publisher and re-establish replication from there. OR if you want we can try to work through removing records from msrepl_commands and msrepl_transactions for that database in the distribution database.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 4, 2011 at 12:29 pm
We're kind of in a bind here with our corporate reporting...I've opened a call with MS tech support - see where that goes...
🙁
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 4, 2011 at 12:33 pm
Sounds like a good choice to use the call at this point. I'll be curious to see what you end up doing to get it working.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 4, 2011 at 2:20 pm
You've probably got this covered, but just in case...going back to your original post, you said
After restoring the days full backup (with NORECOVERY), and then restoring a DIFF backup (FULL RECOVERY...
Were there no transaction logs, taken after the DIFF, to restore?
March 4, 2011 at 3:19 pm
No. We had a full down at that point in time the diff was taken.
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 14, 2011 at 10:27 am
What a nightmare making a phone call to Microsoft was...I can't even being to express how much the entire experience was a waste of both the time and money spent. OMG - the guy I had spent an hour doing the things I'd already tried, another 2 hours telling me to hold on while he conferred with his technical specialist and another 2 hours rerunning the same commands he had tried in the first hour. I swear...MS SHOULD HAVE PAID ME to have gone through that experience
After those hourse were wasted he came back to tell me that he thought the best thing was to disable replication altogether and completely start over... At that point I told them I was willing to bet $$$ that I could accomplish the task more efficiently than they would and dropped them from the call.
90 mins later I had everything back up and running.
Shizza!!!
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 14, 2011 at 8:57 pm
I typically force escalation on replication issues due to some of what you describe. I'll leave it at that.
Glad you got it fixed.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 14, 2011 at 9:16 pm
Thanks again for all your help! Much appreciated it.
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
November 7, 2015 at 2:58 am
We have the exactly same issue happening right now. Curious how did this finally got fixed?
November 7, 2015 at 9:59 am
I had to completely disable replication altogether and start over.
In retrospect, I believe if I had run the distribution cleanup agents prior to attempting to re-add the publications, it might have done the trick - but too late to tell if that would have worked 🙂
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
July 13, 2023 at 1:15 pm
Viewing 13 posts - 16 through 27 (of 27 total)
You must be logged in to reply to this topic. Login to reply