December 11, 2002 at 3:42 am
I have implemented the Log Shipping for the publication DB. Its works fine. As of making transactional logs to the stand by server and the replication doesnt not happen twice.
But now i am not able to do the role change, Can someone tell me which method to do, as there r 2 methods which r specified in BOL. The one is that resolve logins and change role SP and the other is specified in BOL when u search for "Transactional Replication and Log Shipping" with quotes, which says about the semi synchronous mode. I tried both the ways but seems not to be working.
Can any1 tell me how to rename the computer name and when i run the "sp_replrestart" it throws the foll error
Could not find stored procedure ''
Have any1 implement log shipping with transactional replication, please help me.
December 16, 2002 at 8:00 am
This was removed by the editor as SPAM
December 16, 2002 at 5:35 pm
Why are you using two different tools that effectively accomplish the same thing? If there is already transactional replication going, why not just add a subscription for the Log shipped machine, and do away with the log shipping to start with. I've seen both used in many different situations, but never together. I know its not really answering your question, but I am curious.
December 16, 2002 at 9:25 pm
quote:
Why are you using two different tools that effectively accomplish the same thing? If there is already transactional replication going, why not just add a subscription for the Log shipped machine, and do away with the log shipping to start with. I've seen both used in many different situations, but never together. I know its not really answering your question, but I am curious.
Well our scenario is whenever the main server goes down, all the roles of the main server such as replication and the application will be pointing to the stand by server. Our application takes data from hetregenous databases and put it into the main server and these data gets replicated to the subscribers. Now we have to create the back up server in such a way that when ever the main server goes down the application will point to the back up server , and the data will come to the back up server and from there it will be replicated to different subscribers.
I hope i have explained the situation, Can u tell me how to do this and is there any other method of implementing the similar scenario
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply