|
|
You're in the
sql server replication
group:Creating Snapshot Subscription: Can't choose Don't Initialize Schema and Data
sql server replication:
Hello,
Sorry for the long message! I have been trying to figure this out for a few days, reading BOL, reading newsgroups, reading MS's site, but I am still getting this error. I made a snapshot publication, and I am trying to make a new subscription, and on the page to Initialize Subscription, the option for "NO, the Subscriber has the schema and data already" is greyed out... the two databases are similar in schema. The subscriber has different data in there already, and we want to push data from the publisher to the subscriber (and not send it back if there are any changes). Also, the subscriber will have new data put into it and potentially update the data sent over from the publisher (although, changes not to be sent back so Merge replication not required). Does it think the subscriber has a different schema or something? Any ideas? I am about give up and write my own custom routine with XML! Thanks,
Hilary, Thank you very much for your reply. Yes, the subscription has it's own data and will have it's own data (and it might also modify the data replicated from the publisher). I specified 'Keep existing table unchanged' for the articles but I am still not able to choose 'Don't Initialize Schema and Data' when I try to configure a new push subscription. ?? I don't understand exactly what you mean by #2... are you asking if I want to Publisher to be able to delete data on the subscriber? No, I don't want the publisher to delete data on the subscriber that is the subscriber's data... is there a chance this could happen if I don't specify a filter row clause? Your book would probably help, it is too bad my local store does not have it! I need to get this working this week, may have to call MS. If you have any other ideas, I would appreciate your ideas. Regards, -ed [quoted text, click to view] Hilary Cotter wrote:
> I'm a little confused. > > From what you describe it sounds like you have data already in your > Subscriber, and want to push more data through a snapshot publication > without loosing the data that is already there. > > If this is the case you have two options: > > 1) when you are creating your snapshot publication, and get to the specify > articles dialog box, click on the three ellipses/browse button to the right > of your article. In the Snapshot tab, for Name Conflicts select Keep > existing table unchanged. > 2) if you only want delete the data that the publisher owns, you will have > to identify a column or columns that can be used to identify data coming > from the publisher. Then in the name conflicts section select delete data in > the table that matches the row filter statement. Then select "Yes, I will > define data filters, enable anonymous subscriptions, or customize other > properites" in the Customize the Properties of the Publication dialog, > select horizontal filtering, and then add the restriction in the filter rows > fitler clause. > > Does this help?
I'm a little confused.
From what you describe it sounds like you have data already in your Subscriber, and want to push more data through a snapshot publication without loosing the data that is already there. If this is the case you have two options: 1) when you are creating your snapshot publication, and get to the specify articles dialog box, click on the three ellipses/browse button to the right of your article. In the Snapshot tab, for Name Conflicts select Keep existing table unchanged. 2) if you only want delete the data that the publisher owns, you will have to identify a column or columns that can be used to identify data coming from the publisher. Then in the name conflicts section select delete data in the table that matches the row filter statement. Then select "Yes, I will define data filters, enable anonymous subscriptions, or customize other properites" in the Customize the Properties of the Publication dialog, select horizontal filtering, and then add the restriction in the filter rows fitler clause. Does this help? -- Hilary Cotter Looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html [quoted text, click to view] "Ed West" <west@westville.com> wrote in message news:eaEgORghEHA.2544@TK2MSFTNGP10.phx.gbl... > Hello, > > Sorry for the long message! I have been trying to figure this out for a > few days, reading BOL, reading newsgroups, reading MS's site, but I am > still getting this error. I made a snapshot publication, and I am > trying to make a new subscription, and on the page to Initialize > Subscription, the option for "NO, the Subscriber has the schema and data > already" is greyed out... the two databases are similar in schema. > > The subscriber has different data in there already, and we want to push > data from the publisher to the subscriber (and not send it back if there > are any changes). Also, the subscriber will have new data put into it > and potentially update the data sent over from the publisher (although, > changes not to be sent back so Merge replication not required). > > Does it think the subscriber has a different schema or something? > > Any ideas? I am about give up and write my own custom routine with XML! > > Thanks, > > -ed
Hi I called Microsoft, I can't do what I want to do with Snapshot, I need transactional. But MSDE does not allow the publisher to do transactional replication, which is what I want to do. anyway, thanks for your help. -dan [quoted text, click to view] Ed West wrote:
> > Hilary, > > Thank you very much for your reply. Yes, the subscription has it's own > data and will have it's own data (and it might also modify the data > replicated from the publisher). > > I specified 'Keep existing table unchanged' for the articles but I am > still not able to choose 'Don't Initialize Schema and Data' when I try > to configure a new push subscription. ?? > > I don't understand exactly what you mean by #2... are you asking if I > want to Publisher to be able to delete data on the subscriber? No, I > don't want the publisher to delete data on the subscriber that is the > subscriber's data... is there a chance this could happen if I don't > specify a filter row clause? > > Your book would probably help, it is too bad my local store does not > have it! I need to get this working this week, may have to call MS. > > If you have any other ideas, I would appreciate your ideas. > > Regards, > > -ed > > > Hilary Cotter wrote: > >> I'm a little confused. >> >> From what you describe it sounds like you have data already in your >> Subscriber, and want to push more data through a snapshot publication >> without loosing the data that is already there. >> >> If this is the case you have two options: >> >> 1) when you are creating your snapshot publication, and get to the >> specify >> articles dialog box, click on the three ellipses/browse button to the >> right >> of your article. In the Snapshot tab, for Name Conflicts select Keep >> existing table unchanged. >> 2) if you only want delete the data that the publisher owns, you will >> have >> to identify a column or columns that can be used to identify data coming >> from the publisher. Then in the name conflicts section select delete >> data in >> the table that matches the row filter statement. Then select "Yes, I will >> define data filters, enable anonymous subscriptions, or customize other >> properites" in the Customize the Properties of the Publication dialog, >> select horizontal filtering, and then add the restriction in the >> filter rows >> fitler clause. >> >> Does this help?
the don't initialize schema and data option is not available for Snapshot
replication. Re: #2 The keep the existing table unchanged will NOT delete the data in the table on the Subscriber. You may however run into problems if there are pk's on this table and some of the data coming from the snapshot publication is the same. -- Hilary Cotter Looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html [quoted text, click to view] "Ed West" <west@westville.com> wrote in message news:u2YsBMihEHA.3612@TK2MSFTNGP12.phx.gbl... > > Hilary, > > Thank you very much for your reply. Yes, the subscription has it's own > data and will have it's own data (and it might also modify the data > replicated from the publisher). > > I specified 'Keep existing table unchanged' for the articles but I am > still not able to choose 'Don't Initialize Schema and Data' when I try > to configure a new push subscription. ?? > > I don't understand exactly what you mean by #2... are you asking if I > want to Publisher to be able to delete data on the subscriber? No, I > don't want the publisher to delete data on the subscriber that is the > subscriber's data... is there a chance this could happen if I don't > specify a filter row clause? > > Your book would probably help, it is too bad my local store does not > have it! I need to get this working this week, may have to call MS. > > If you have any other ideas, I would appreciate your ideas. > > Regards, > > -ed > > > Hilary Cotter wrote: > > > I'm a little confused. > > > > From what you describe it sounds like you have data already in your > > Subscriber, and want to push more data through a snapshot publication > > without loosing the data that is already there. > > > > If this is the case you have two options: > > > > 1) when you are creating your snapshot publication, and get to the specify > > articles dialog box, click on the three ellipses/browse button to the right > > of your article. In the Snapshot tab, for Name Conflicts select Keep > > existing table unchanged. > > 2) if you only want delete the data that the publisher owns, you will have > > to identify a column or columns that can be used to identify data coming > > from the publisher. Then in the name conflicts section select delete data in > > the table that matches the row filter statement. Then select "Yes, I will > > define data filters, enable anonymous subscriptions, or customize other > > properites" in the Customize the Properties of the Publication dialog, > > select horizontal filtering, and then add the restriction in the filter rows > > fitler clause. > > > > Does this help? > >
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 |