October 9, 2008 at 8:29 am
Hi, I have a problem that I have run into with SQL transaction replication. I work for an ASP that hosts an oracle application called JD Edwards Enterprise one.
When updates are applied (ESU) to the app, any DDL statements that run that add or alter indexes or columns fails with a marked for replication message. Only way around this that I can see is to drop the publication and subscription and recreate it.
Using the snapshot is not an option due to limited bandwidth, T-1. The entire database is replicated and is 150GB. With that being said I also will need to get these changes over to the subscriber database. Is there any other way to do this without dropping the publication?
Ideally I would like the application to make the changes instead of manually running the sql statements. But I don’t know if this is possible. Biggest challenges I see is getting this to work without having to do a manual resynchronize replication subscriptions.
Replication was setup using KB320499.
SQL 2000EE SP4
Windows 2003 EE SP2
Server A, Publisher with push subscription, Seattle
Server B, Subscriber , Georgia
Thanks for your time.
October 10, 2008 at 12:49 pm
If my memory serves me well, I believe you cannot replicate DDL (like adding a column to a publishing table and expecting the DDL will be replicated over to the subscriber side).
If the new column needs to be replicated, then you need to resetup the replication.
By upgrading this sql 2K5 will solve your problem.
HTH,
JY
October 16, 2008 at 2:30 am
if it is a DDL Change just drop the ariticle and subscription and then recreate it.
--dropping the aricle
1)sp_dropsubscription
2)sp_droparticle
--create article
3)sp_addarticle
4)sp_addsubscription
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply