Replicate Stored Procedure Execution

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by Andy Warren » Replicate Stored Procedure Execution

Replicate Stored Procedure Execution

Rate Topic

Display Mode

Topic Options

Author

Message

Andy Warren

Posted Sunday, November 04, 2007 8:17 AM

SSCertifiable

Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462, Visits: 1,384

Comments posted to this topic are about the item Replicate Stored Procedure Execution

Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter

Post #418302

sql_er

Posted Monday, November 05, 2007 8:08 AM

SSC Veteran

Group: General Forum Members
Last Login: Friday, May 03, 2013 10:08 AM
Points: 223, Visits: 424

What if a new stored procedure is added to the publisher, will it be propagated to all the subscribers as well or should it be added in some special way for the propagation to take affect?

Thank you

Post #418583

Andy Warren

Posted Monday, November 05, 2007 8:20 AM

SSCertifiable

Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462, Visits: 1,384

You add it normally to the publisher, then you'd have to manually check it as an article in the pub. From there replication handles pushing it to the subscribers.

Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter

Post #418593

Asaf Meir

Posted Tuesday, November 06, 2007 11:32 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, November 10, 2010 11:31 PM
Points: 1, Visits: 17

Is there a chance to have the data changes (in the employee table) replicated and the have the data changes applied by the SP execution by the subscribers too?
this is an unnecessary redundancy.

Post #419447

Andy Warren

Posted Wednesday, November 07, 2007 6:37 AM

SSCertifiable

Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462, Visits: 1,384

No, its smart enough to figure that out.

Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter

Post #419576

ruben.ortiz

Posted Thursday, July 22, 2010 2:42 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, July 23, 2010 5:10 AM
Points: 3, Visits: 12

Hello

maybe it is a stupid question but...why names of stored procedures are different in subscriber?

Post #956999

Andy Warren

Posted Thursday, July 22, 2010 5:59 AM

SSCertifiable

Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462, Visits: 1,384

Ruben, I don't that happens by default, either someone renamed them in the publication or they were renamed directly.

Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter

Post #957095

ruben.ortiz

Posted Thursday, July 22, 2010 7:17 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, July 23, 2010 5:10 AM
Points: 3, Visits: 12

Hi Andy

I have setup a replication betweeen two sql servers, and I am having problems with replication of stored procedures. In fact, I'm reading your article to find some solution to my problem.

I want replication of Stored Procedures will be exactly the same of Publisher/Distributor. Because developers usually modify stored procedures and I want this changes will replicate in subscriptor.

I have noticed Views and tables are well replicated (exactly the same tables and same views) but in Stored Procedures I see Stored that doesn't exist in Publisher ¿? Just like you post (in image)on your article.

And actually I don't know if this is ok or not.

Thanks by your reply :) I'm going to continue doing some test.

Best regards

Ruben O.

Post #957160

GabyYYZ

Posted Tuesday, May 03, 2011 2:24 PM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 12:30 PM
Points: 795, Visits: 1,985

I know I'm a bit late with this question but hopefully someone still reads this article (which I found fantastically useful). Smile

Let's say I have a table replicated from publisher to subscriber. I need to update a MASSIVE amount of rows, by nullifying certain columns no longer used (unfortunately can't drop the column itself as it would force downtime when re-snapping). I've created a proc in our QA environment, replicating the execution as in the article (not serializable) that updates the rows on the publisher side.

Now what I have down, on the subscriber side, the proc which was replicated, I have now wrapped in a huge comment block, so when it is executed in the publisher, the execution call to the subscriber does nothing, but still runs. The idea is that the subscriber keep those columns filled in, to be possibly null'ed later on.

My big question, is there an issue having the actual data different between the two tables, even though the number of rows are the same, and all other data is the same, especially going forward with standard updates/inserts/deletes?

Thanks!

Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein

Post #1102704

« Prev Topic | Next Topic »

Permissions