Replicating changed DB
From: news.microsoft.com (markNOSPAM_at_sitereportsltd.com)
Date: 05/18/04
- Next message: news.microsoft.com: "Re: Schema changes"
- Previous message: Ciaran: "No Data Needed To be Merged - But Only for INSERT ???"
- Next in thread: Paul Ibison: "Re: Replicating changed DB"
- Reply: Paul Ibison: "Re: Replicating changed DB"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 12:04:48 +0100
Hi,
I have an SQL 2k database on a dedicated server in another city which I need
to replicate to a backup server in the office. The replication aspect is not
a problem except that the database tables are changed from time to time,
sometimes a new column or changing an existing column. Whilst we do have a
development database, the changes still need to go live at some stage. As EM
will not allow me to drop a specific article I have to resort to dropping
the publication and re-creating it. With a 20gb database this is not a 5
minute job and it takes 2-3 days to re-sync the backup. There must be a way
to replicate structural changes to a database, without scrapping a 20gb
snapshot and re-building. Surely it is just a case of replicating the alter
table statements(s)?
We are using transactional push replication (we have problems getting pull
to work through ISA) between two SQL 2k servers
Any help greatly appreciated, thanks.
Mark Leavesley
- Next message: news.microsoft.com: "Re: Schema changes"
- Previous message: Ciaran: "No Data Needed To be Merged - But Only for INSERT ???"
- Next in thread: Paul Ibison: "Re: Replicating changed DB"
- Reply: Paul Ibison: "Re: Replicating changed DB"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|