July 9, 2012 at 12:00 pm
Hi,
I'm no DBA, so I'd happily take an advice or two!
I have 4 SQL Server 2000 servers, located in 4 geographical sites. The servers are replicated (merge). It works fine.
Now, I must do some design changes on replicated tables and modify a few StoredProc. Also, I must purge a couple years of useless data (about 4-5 millions rows in 12 tables).
What is the best way to do this?
I thought about stopping the replication, run a script to apply the design changes, purge the master (distributed) database, back it up, zip the .bak (about 500-600 megs), copy it to the others sites, restore the backup and restart the replication.
Is there an easier way and more efficient way to do this?? Because I'd have to shutdown the production on all 4 sites for the duration of this lengthy process, so if there is a fastest way, I'd be happy to know!
thanks for your time and help
July 9, 2012 at 3:15 pm
You may want to check out this article on schema changes in replicated databases:
Schema Changes on Publication Databases
You can plan to have your table changes replicated to your subscribers. The stored procedure I think will have to be created at each site. As for the deletes, you might want to look into changing the replication agent properties to see if you can increase the batch commands to reduce overhead for the deletes replicating across.
Joie Andrew
"Since 1982"
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply