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 12»»

Moving Replicated Databases Expand / Collapse
Author
Message
Posted Monday, January 30, 2006 2:59 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Tuesday, August 12, 2014 10:53 AM
Points: 6,783, Visits: 1,876
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/awarren/movingreplicateddatabases.asp

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #254555
Posted Wednesday, February 1, 2006 8:08 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Thursday, August 9, 2007 1:24 PM
Points: 507, Visits: 1

Clever, but I don't recommend doing this at all. You are really risking getting things really screwed up! You are better off just scripting out replication including the jobs, removing it totally (sp_removedbreplication and the jobs), detaching, attaching, and just running the replication script again..It is a little longer, I know but alot safer in the long run..The problem with clever little shortcuts like this is they can fill volumes with what they don't tell you can go wrong! Don't gamble with your databases with cute little workarounds like this. You will probably regret it sooner or later. Stick to what has been tried, true, and tested. DBA's that start experimenting with things like this usually find themselves looking for another job...trust me I have seen it far too often.

Travis Lee Alltop

Sr. SQL Server DBA




Post #254943
Posted Friday, February 3, 2006 8:07 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 4:43 PM
Points: 1,581, Visits: 6
Well, I can be help full in cases you have very big publications and re applying the snapshot takes a very long time. I would really test it in my databases before trying it out in a production environment, but supose that something goes wrong, you can always recreate the publications again.


Post #255816
Posted Monday, March 20, 2006 1:06 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, December 19, 2007 1:07 AM
Points: 11, Visits: 4


It is a good Solution for Moving Replicated Databases



Atul Varshney  




Kindest Regards,

Atul Varshney

Post #266806
Posted Monday, March 20, 2006 1:12 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, December 19, 2007 1:07 AM
Points: 11, Visits: 4
good


Kindest Regards,

Atul Varshney

Post #266809
Posted Monday, March 20, 2006 4:53 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Tuesday, August 12, 2014 10:53 AM
Points: 6,783, Visits: 1,876

Travis,

I understand your position, but its just a matter of mitigating the risk isnt it? Aside from that, what do you think could go wrong with this approach?



Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #267133
Posted Thursday, February 1, 2007 8:06 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, August 11, 2014 6:19 PM
Points: 988, Visits: 1,645

"I ran into this a couple years ago..."

Nice solution, but it was discussed on this forum three years ago and you may remember this topic...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=65&messageid=14226#bm70809




Post #341890
Posted Friday, February 2, 2007 6:01 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Tuesday, August 12, 2014 10:53 AM
Points: 6,783, Visits: 1,876
Its an older article, Steve sometimes will rerun one that he thinks is interesting on Friday.

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #341995
Posted Saturday, February 3, 2007 4:45 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, August 11, 2014 6:19 PM
Points: 988, Visits: 1,645
"That's a nice trick, wish I had known it a few months earlier! Andy http://www.sqlservercentral.com/columnists/awarren/
Andy
http://www.endtoendtraining.com/"



Post #342279
Posted Monday, February 5, 2007 2:12 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 8:36 AM
Points: 5,308, Visits: 9,700

Andy

Why not just back up the database and restore it to the new location?  You don't have to touch the system tables then.

John

Post #342371
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse