March 8, 2011 at 2:22 pm
Hello,
I am trying to change varcher 50 to nvarcher 255 on the field and get an error message,that I can't do it because this table Cannot drop the table because it is being used for replication.
How can I modify the table?
Thank you
March 8, 2011 at 3:17 pm
i) remove from replication
ii) make changes
iii) re-sync. This will take a fresh snapshot.
March 9, 2011 at 12:46 pm
re-sync. This will take a fresh snapshot.
Do you mean reinitialize subscription? if yes do I get new snapshot or original?
March 9, 2011 at 1:21 pm
Krasavita (3/9/2011)
re-sync. This will take a fresh snapshot.Do you mean reinitialize subscription? if yes do I get new snapshot or original?
Correct i mean re-intialize. Will copy over a fresh snapshot to the subscriber.
March 9, 2011 at 1:38 pm
it is not working, I don't see data.
This is what I did:
rclick
reinitialized
use a new snapshot
reinitialize a new snapshot now
mark for reinitialization
March 10, 2011 at 6:26 am
mY publication tab IS SHOWING poor performance
March 10, 2011 at 11:51 am
Krasavita (3/10/2011)
mY publication tab IS SHOWING poor performance
Did you change the table you wanted to change? you should be able to find some good article online. Let us know how it goes. Thanks
March 10, 2011 at 11:55 am
Yes, I changed table,but results are not replicated
March 10, 2011 at 1:37 pm
Krasavita (3/10/2011)
Yes, I changed table,but results are not replicated
When you say results are not replicated are you saying the physical object change did not replicate or you are not replicating data?
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 10, 2011 at 1:43 pm
Both
March 10, 2011 at 1:47 pm
Krasavita (3/10/2011)
Both
So, you pulled the table out of replication, made a change and put it back in replication? Did you send a new snapshot? At this point it would be best if you told me exactly what you did and hopefully I can help a bit to find the solution. 🙂
Let me know the details. Thanks!
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 10, 2011 at 1:54 pm
1.Removed out of the replication
2.Modified table
3.added to the replication
4.Reinitialized with a new snapshot.
I already did it bunch of times and when I do it renitialized and check monitor it showing critical performance and then later poor.
Please help me.
Thank you so much
March 10, 2011 at 2:01 pm
Did you put the table back in the same publication? Are there other tables in that publication? Here is my recommendation to get this fixed.
1. Pull the table out of that publication
2. Put it in a new publication
3. Before adding the subscription right click on the new publication, select properties, under subscription options set independent agent (top option) to false. Click ok.
4. Create the subscription, and in the process of creating it set the snapshot to run immediately. Complete the subscription creation.
5. Right click on the publication and check snapshot agent status. If it hasn't run yet then run that. If it has run or is running let it go and watch to completion.
6. Right click on the subscription and select View Synchronization Status to ensure that you are seeing information there.
This is a "hard reset" type of fix so please understand that your subscriber is going to have the table dropped and a new copied down.
Let me know if you have questions or concerns with this. We should be able to work through fixing it differently as well but this will get you working the quickest.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 10, 2011 at 2:09 pm
Did you put the table back in the same publication? Are there other tables in that publication?
Yes, I put the table in the publication and yes there is other tables in this publications
March 10, 2011 at 2:13 pm
In that situation getting the snapshot to recognize the changes can be sometimes problematic. The steps I sent should work IF you are ok with pushing a new copy of the table to the subscriber.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Viewing 15 posts - 1 through 15 (of 30 total)
You must be logged in to reply to this topic. Login to reply