Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Match Procs Across Servers Expand / Collapse
Author
Message
Posted Friday, May 23, 2014 3:08 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 2:48 PM
Points: 1,125, Visits: 3,612
We are running two side by side reporting servers, one as the live server and one as a failover. When a proc is created or altered on the live server the same should be done on the failover. Currently this is done by changing the connection from one server the to other and repeating whatever was done. What we'd like is some sort of fail-safe so if the change isn't made on the failover it is picked up and done automatically. I'll be able to write something that picks up those procs that have been created\altered on one server but not the other but I'd like some advice about how to go about scripting out the required procs and making the appropriate changes, if indeed that's possible. We may be able to go with third party tools but I think they may have to be a last resort. Any suggestions?


On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" ... I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
—Charles Babbage, Passages from the Life of a Philosopher

How to post a question to get the most help
Post #1573938
Posted Saturday, May 24, 2014 11:26 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 11:52 AM
Points: 2,832, Visits: 8,513
Replication ??


Post #1574324
Posted Sunday, May 25, 2014 12:40 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 8:38 PM
Points: 35,371, Visits: 31,912
Clustering/mirroring for the failover box should already be doing this for you.

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1574359
Posted Tuesday, May 27, 2014 1:15 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 2:48 PM
Points: 1,125, Visits: 3,612
Thanks for the replies but I think I've now got more questions than I had before. What's the best way of checking that clustering, mirroring and replication are set up and running right? We're 'only' the Reporting Team and there's not a massive amount of DBA experience about. We can query the databases and make a beautiful whizzy report to show you pretty much anything you want, but if you ask us how things are running then there's only so much we can do. Yes, there is recruitment going on for a DBA but until then we're a bit in the dark.


On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" ... I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
—Charles Babbage, Passages from the Life of a Philosopher

How to post a question to get the most help
Post #1574670
Posted Wednesday, May 28, 2014 8:59 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 11:52 AM
Points: 2,832, Visits: 8,513
When you set up replication, you generally also set up scheduled job to replicate data at a specified interval. You can get an alert if those jobs fail.

You could also set up a job to check that a few of your replicated tables have current data in them. Either check that data values are current, or use a linked server to compare against the publisher's tables. Send an email alert if any discrepancy is greater than the replication frequency.



Post #1575427
Posted Thursday, May 29, 2014 5:46 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 5:31 AM
Points: 433, Visits: 982
You could write something in Powershell to cycle through the procs and functions, comparing source and target versions, and updating as needed.



Post #1575529
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse