|
|
You're in the
sql server replication
group:Merge Replication - remove article
sql server replication:
replication all over again. You of course can drop an article but make sure they don't have connections with other articles. (foreign keys, views, SPs etc.) And then you'll need to recreate the snapshot and synch with your subscribers. If you are using SQL 2000 then follow the article that I sent its link. -- Ekrem Önsoy [quoted text, click to view] "Regina" <Regina@discussions.microsoft.com> wrote in message
news:287A3182-5E15-42A1-8279-2CF97DADB147@microsoft.com... > Ok, so I can not drop a table from the replication and then run the > snapshot > job after. The only way to do this is to uninstall the replication and > install it without the tables. > > "Ekrem Önsoy" wrote: > >> Hi Regina, >> >> >> Removing an article from a publication invalidates the existed snapshot. >> >> You may want to check out the BOL about this: >> http://msdn2.microsoft.com/en-us/library/ms152493.aspx >> >> >> -- >> Ekrem Önsoy >> >> >> >> >> "Regina" <Regina@discussions.microsoft.com> wrote in message >> news:6BD3254A-BD6D-4DCB-9668-FD9B76523206@microsoft.com... >> > Hi >> > I have a question about merge replication. We hav one server as master >> > and >> > 3 >> > subscribers. In prodoktion we have noticed that the replikation takes >> > time >> > that we wish to reduce. one way to try to reduce the time is to drop >> > two >> > articles from the merge replication. When I was trying this on our >> > developmaster I right-clicked on the master replication and clicked >> > properties. After choosing Articles tab (where I add articles to the >> > replication) there are checkboxes in front of every row. If I want to >> > uncheck >> > an article and drop it from the replication but still keep it in the >> > database >> > why is the checkbox in front of the articles greyed out. What is the >> > easyest >> > way to remove an article from the replication? After dropping is always >> > snapshot nessecary? Can I make the snapshot go faster? >> > >> > Thanks in advance. >> > //Regina >>
Hi Regina,
Removing an article from a publication invalidates the existed snapshot. You may want to check out the BOL about this: http://msdn2.microsoft.com/en-us/library/ms152493.aspx -- Ekrem Önsoy [quoted text, click to view] "Regina" <Regina@discussions.microsoft.com> wrote in message
news:6BD3254A-BD6D-4DCB-9668-FD9B76523206@microsoft.com... > Hi > I have a question about merge replication. We hav one server as master and > 3 > subscribers. In prodoktion we have noticed that the replikation takes time > that we wish to reduce. one way to try to reduce the time is to drop two > articles from the merge replication. When I was trying this on our > developmaster I right-clicked on the master replication and clicked > properties. After choosing Articles tab (where I add articles to the > replication) there are checkboxes in front of every row. If I want to > uncheck > an article and drop it from the replication but still keep it in the > database > why is the checkbox in front of the articles greyed out. What is the > easyest > way to remove an article from the replication? After dropping is always > snapshot nessecary? Can I make the snapshot go faster? > > Thanks in advance. > //Regina
Hi
I have a question about merge replication. We hav one server as master and 3 subscribers. In prodoktion we have noticed that the replikation takes time that we wish to reduce. one way to try to reduce the time is to drop two articles from the merge replication. When I was trying this on our developmaster I right-clicked on the master replication and clicked properties. After choosing Articles tab (where I add articles to the replication) there are checkboxes in front of every row. If I want to uncheck an article and drop it from the replication but still keep it in the database why is the checkbox in front of the articles greyed out. What is the easyest way to remove an article from the replication? After dropping is always snapshot nessecary? Can I make the snapshot go faster? Thanks in advance.
Ok, so I can not drop a table from the replication and then run the snapshot
job after. The only way to do this is to uninstall the replication and install it without the tables. [quoted text, click to view] "Ekrem Önsoy" wrote:
> Hi Regina, > > > Removing an article from a publication invalidates the existed snapshot. > > You may want to check out the BOL about this: > http://msdn2.microsoft.com/en-us/library/ms152493.aspx > > > -- > Ekrem Önsoy > > > > > "Regina" <Regina@discussions.microsoft.com> wrote in message > news:6BD3254A-BD6D-4DCB-9668-FD9B76523206@microsoft.com... > > Hi > > I have a question about merge replication. We hav one server as master and > > 3 > > subscribers. In prodoktion we have noticed that the replikation takes time > > that we wish to reduce. one way to try to reduce the time is to drop two > > articles from the merge replication. When I was trying this on our > > developmaster I right-clicked on the master replication and clicked > > properties. After choosing Articles tab (where I add articles to the > > replication) there are checkboxes in front of every row. If I want to > > uncheck > > an article and drop it from the replication but still keep it in the > > database > > why is the checkbox in front of the articles greyed out. What is the > > easyest > > way to remove an article from the replication? After dropping is always > > snapshot nessecary? Can I make the snapshot go faster? > > > > Thanks in advance. > > //Regina
OK, thanks for your help. I´ve read the aricle and when I tried on the
Articles page of the Publication Properties - <Publication> dialog box, clear the check box next to each article you want to delete I couldn´t The check box is greyd out. do you have any Idea why Thanks a lot for your help. //Regina [quoted text, click to view] "Ekrem Önsoy" wrote:
> Well, there is a misunderstanding I guess. You don't have to setup > replication all over again. > > You of course can drop an article but make sure they don't have connections > with other articles. (foreign keys, views, SPs etc.) > > And then you'll need to recreate the snapshot and synch with your > subscribers. > > If you are using SQL 2000 then follow the article that I sent its link. > > > -- > Ekrem Önsoy > > > > "Regina" <Regina@discussions.microsoft.com> wrote in message > news:287A3182-5E15-42A1-8279-2CF97DADB147@microsoft.com... > > Ok, so I can not drop a table from the replication and then run the > > snapshot > > job after. The only way to do this is to uninstall the replication and > > install it without the tables. > > > > "Ekrem Önsoy" wrote: > > > >> Hi Regina, > >> > >> > >> Removing an article from a publication invalidates the existed snapshot. > >> > >> You may want to check out the BOL about this: > >> http://msdn2.microsoft.com/en-us/library/ms152493.aspx > >> > >> > >> -- > >> Ekrem Önsoy > >> > >> > >> > >> > >> "Regina" <Regina@discussions.microsoft.com> wrote in message > >> news:6BD3254A-BD6D-4DCB-9668-FD9B76523206@microsoft.com... > >> > Hi > >> > I have a question about merge replication. We hav one server as master > >> > and > >> > 3 > >> > subscribers. In prodoktion we have noticed that the replikation takes > >> > time > >> > that we wish to reduce. one way to try to reduce the time is to drop > >> > two > >> > articles from the merge replication. When I was trying this on our > >> > developmaster I right-clicked on the master replication and clicked > >> > properties. After choosing Articles tab (where I add articles to the > >> > replication) there are checkboxes in front of every row. If I want to > >> > uncheck > >> > an article and drop it from the replication but still keep it in the > >> > database > >> > why is the checkbox in front of the articles greyed out. What is the > >> > easyest > >> > way to remove an article from the replication? After dropping is always > >> > snapshot nessecary? Can I make the snapshot go faster? > >> > > >> > Thanks in advance. > >> > //Regina > >>
This is very much SQL 2005 functionality. If you're using SQL 2000 then
you'll need to drop the subscriptions, drop the article and then initialize. HTH, Paul Ibison
Thanks for your help Paul and Ekrem. But I have one more question. If the
only possibility to drop a article from the merge replication after snapshot job has been run is to drop the subscription and initialize it ( by that du you meen uninstall it and install it with the wizard again) why is there a procedure with the name sp_dropmergearticle. I tryed using this procedure as below EXEC sp_dropmergearticle @publication = 'pub_bilbo', @article = 'test_table', @force_invalidate_snapshot = 1; Cannot drop article 'test_table' from publication 'pub_bilbo' because its snapshot has been run and this publication could have active subscriptions. thanks again Regina but got following error [quoted text, click to view] "Paul Ibison" wrote:
> This is very much SQL 2005 functionality. If you're using SQL 2000 then > you'll need to drop the subscriptions, drop the article and then initialize. > HTH, > Paul Ibison
sp_dropmergearticle is an alternative of GUI. You can do that job either
way. Also, the following code that you wrote works for me. It's correct, no problem. It must be being used or linked to another article. Follow its track. -- Ekrem Önsoy [quoted text, click to view] "Regina" <Regina@discussions.microsoft.com> wrote in message
news:11FD3A23-ACE5-4E5B-A78D-C698694EEA72@microsoft.com... > Thanks for your help Paul and Ekrem. But I have one more question. If the > only possibility to drop a article from the merge replication after > snapshot > job has been run is to drop the subscription and initialize it ( by that > du > you meen uninstall it and install it with the wizard again) why is there a > procedure with the name sp_dropmergearticle. I tryed using this procedure > as > below > > EXEC sp_dropmergearticle > @publication = 'pub_bilbo', > @article = 'test_table', > @force_invalidate_snapshot = 1; > > Cannot drop article 'test_table' from publication 'pub_bilbo' because its > snapshot has been run and this publication could have active > subscriptions. > > thanks again > Regina > > but got following error > "Paul Ibison" wrote: > >> This is very much SQL 2005 functionality. If you're using SQL 2000 then >> you'll need to drop the subscriptions, drop the article and then >> initialize. >> HTH, >> Paul Ibison >>
hmmmm, ok. I use MS SQL Server 2000 and I get the error I wrote below. The
table is a test table I added and does not have any links to other tables. If I look at view dependencies I get a list, MSMerge_contents_testtable sel_D........ sp_ins_D........ sp_sel_D.... sp_sel_D.... sp_upd_D.... I guess all this views and procedures has to do with the merge. Or am I wrong? How is it my code does not work if it works for you. [quoted text, click to view] "Ekrem Önsoy" wrote:
> sp_dropmergearticle is an alternative of GUI. You can do that job either > way. > > Also, the following code that you wrote works for me. It's correct, no > problem. > > It must be being used or linked to another article. Follow its track. > > -- > Ekrem Önsoy > > > > > "Regina" <Regina@discussions.microsoft.com> wrote in message > news:11FD3A23-ACE5-4E5B-A78D-C698694EEA72@microsoft.com... > > Thanks for your help Paul and Ekrem. But I have one more question. If the > > only possibility to drop a article from the merge replication after > > snapshot > > job has been run is to drop the subscription and initialize it ( by that > > du > > you meen uninstall it and install it with the wizard again) why is there a > > procedure with the name sp_dropmergearticle. I tryed using this procedure > > as > > below > > > > EXEC sp_dropmergearticle > > @publication = 'pub_bilbo', > > @article = 'test_table', > > @force_invalidate_snapshot = 1; > > > > Cannot drop article 'test_table' from publication 'pub_bilbo' because its > > snapshot has been run and this publication could have active > > subscriptions. > > > > thanks again > > Regina > > > > but got following error > > "Paul Ibison" wrote: > > > >> This is very much SQL 2005 functionality. If you're using SQL 2000 then > >> you'll need to drop the subscriptions, drop the article and then > >> initialize. > >> HTH, > >> Paul Ibison > >>
This will only work after you have created the publication and not yet
configured the subscriptions. The same option is available in the GUI at this stage ie the checkboxes against each article aren't greyed out. As you're on SQL 2000 you can not remove this article at your stage - you'll need to "reinitialize" ie script out the publication, drop the publication, readd the publication withoput the subscriptions then remove the article, then readd the subscriptions and initialize. HTH,
Ekrem is quoting from BOL for SQL 2005 which has different functionality.
This is the quote from BOL for SQL 2000: "sp_dropmergearticle is used in merge replication. sp_dropmergearticle is allowed only when there is no active subscription for the current publication. If there is an existing subscription, dropping an article or articles is not allowed.". Please see my other post for more advice on how to "reinitialize" should you decide to go down this path. HTH, Paul Ibison
Ok thanks Paul. How do I do this? There is a choice in 2000 that says
reinitialize all subscriptions. I guess I choose that one. But how do I continue. Thanks [quoted text, click to view] "Paul Ibison" wrote:
> This will only work after you have created the publication and not yet > configured the subscriptions. The same option is available in the GUI at this > stage ie the checkboxes against each article aren't greyed out. As you're on > SQL 2000 you can not remove this article at your stage - you'll need to > "reinitialize" ie script out the publication, drop the publication, readd the > publication withoput the subscriptions then remove the article, then readd > the subscriptions and initialize. > HTH,
For SQL 2000 you're outside the standard boundaries so as I mentioned I'd do
it like this: "ie script out the publication, drop the publication, readd the publication without the subscriptions then remove the article, then readd the subscriptions and initialize." Cheers, Paul Ibison
OHHHH, sorry I´m with you. A little miss from my part. I get it. Thanks
[quoted text, click to view] "Paul Ibison" wrote:
> For SQL 2000 you're outside the standard boundaries so as I mentioned I'd do > it like this: "ie script out the publication, drop the publication, readd the > publication without the subscriptions then remove the article, then readd > the subscriptions and initialize." > Cheers, > Paul Ibison
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |