|
|
You're in the
sql server replication
group:Snapshot Problem
sql server replication:
Domain No Anonymous Subscribers Nothing Fancy Using Sql Query Analyzer (Got burnt by making the change at EM & having = entire snapshot being invalidated once) Script =3D Sp_droparticle - said I had to force invalidate snapshot But after adding the article back & then starting the Snapshot agent, = instead of seeing a snapshot for just that one article, I am seeing the = entire snapshot being generated again. Where have I gone wrong? Do I have something set incorrectly? I don't = want a full snapshot to be generated every time I make a change. Any = way to back door that & have only the one table marked to be snapshot? --=20
Hi Jude
You did nothing wrong. What you perhaps could do is remove the contents of the stored procedure from the article you wish to "drop". This way it will effectively be dropped - in other words the commands won't be applied, but changes will be tracked and the command constructed for it. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Jude" <judes@email.uophx.edu> wrote in message Sql Server 2000 to Sql Server 2000 Transactional Replication - On Same news:OS6ELww4GHA.696@TK2MSFTNGP06.phx.gbl... Domain No Anonymous Subscribers Nothing Fancy Using Sql Query Analyzer (Got burnt by making the change at EM & having entire snapshot being invalidated once) Script = Sp_droparticle - said I had to force invalidate snapshot But after adding the article back & then starting the Snapshot agent, instead of seeing a snapshot for just that one article, I am seeing the entire snapshot being generated again. Where have I gone wrong? Do I have something set incorrectly? I don't want a full snapshot to be generated every time I make a change. Any way to back door that & have only the one table marked to be snapshot? -- JUDE
How can I stop the entire snapshot from being generated now & only get that
one table snapshot? When I started the Snapshot agent the entire snapshot was being generated again & I stopped the agent. By the way, when it says I have to "force invalidate snapshot" am I correct in putting @Force_Invalidate = 1? -- JUDE [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:%23d1XEo74GHA.2536@TK2MSFTNGP06.phx.gbl... > Hi Jude > > You did nothing wrong. What you perhaps could do is remove the contents of > the stored procedure from the article you wish to "drop". This way it will > effectively be dropped - in other words the commands won't be applied, but > changes will be tracked and the command constructed for it. > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Jude" <judes@email.uophx.edu> wrote in message > news:OS6ELww4GHA.696@TK2MSFTNGP06.phx.gbl... > Sql Server 2000 to Sql Server 2000 Transactional Replication - On Same > Domain > No Anonymous Subscribers > Nothing Fancy > > Using Sql Query Analyzer (Got burnt by making the change at EM & having > entire snapshot being invalidated once) > > Script = Sp_droparticle - said I had to force invalidate snapshot > > But after adding the article back & then starting the Snapshot agent, > instead of seeing a snapshot for just that one article, I am seeing the > entire snapshot being generated again. > > Where have I gone wrong? Do I have something set incorrectly? I don't > want a full snapshot to be generated every time I make a change. Any way > to back door that & have only the one table marked to be snapshot? > > -- > JUDE >
I'm sorry I misread your post. Ok, so you have added another article back
in. IIRC if you do this through the wizard the entire snapshot will be generated. If you do it through query analyzer only the added article will be resnapshotted if you are using named subscriptions. If you are using anonymous the entire publication will be resnapshotted. The force_invalidate_snapshot option will bypass a warning message if the change you are making to the publication will break the snapshot and require a new one. If you set this to 0 the procs will raise an error message and the proc will not do its task. If you set it to 1 no message will be raised and the snapshot will be required. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Jude" <judes@email.uophx.edu> wrote in message news:%235lEil94GHA.696@TK2MSFTNGP06.phx.gbl... > How can I stop the entire snapshot from being generated now & only get > that one table snapshot? > > When I started the Snapshot agent the entire snapshot was being generated > again & I stopped the agent. > > By the way, when it says I have to "force invalidate snapshot" am I > correct in putting @Force_Invalidate = 1? > > -- > JUDE > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:%23d1XEo74GHA.2536@TK2MSFTNGP06.phx.gbl... >> Hi Jude >> >> You did nothing wrong. What you perhaps could do is remove the contents >> of the stored procedure from the article you wish to "drop". This way it >> will effectively be dropped - in other words the commands won't be >> applied, but changes will be tracked and the command constructed for it. >> >> -- >> Hilary Cotter >> Director of Text Mining and Database Strategy >> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. >> >> This posting is my own and doesn't necessarily represent RelevantNoise's >> positions, strategies or opinions. >> >> Looking for a SQL Server replication book? >> http://www.nwsu.com/0974973602.html >> >> Looking for a FAQ on Indexing Services/SQL FTS >> http://www.indexserverfaq.com >> >> >> >> "Jude" <judes@email.uophx.edu> wrote in message >> news:OS6ELww4GHA.696@TK2MSFTNGP06.phx.gbl... >> Sql Server 2000 to Sql Server 2000 Transactional Replication - On Same >> Domain >> No Anonymous Subscribers >> Nothing Fancy >> >> Using Sql Query Analyzer (Got burnt by making the change at EM & having >> entire snapshot being invalidated once) >> >> Script = Sp_droparticle - said I had to force invalidate snapshot >> >> But after adding the article back & then starting the Snapshot agent, >> instead of seeing a snapshot for just that one article, I am seeing the >> entire snapshot being generated again. >> >> Where have I gone wrong? Do I have something set incorrectly? I don't >> want a full snapshot to be generated every time I make a change. Any way >> to back door that & have only the one table marked to be snapshot? >> >> -- >> JUDE >> > >
Thanx that makes it clearer, but in my old publication I could easily drop 1
article & then add it back without ever getting a message that I needed to set @Force_Invalidate_Snapshot to 1, and now each time I drop/add back it is telling me I need to do this. I can't seem to pinpoint why. It is a named subscription. -- JUDE [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:es6VVo%234GHA.1900@TK2MSFTNGP02.phx.gbl... > I'm sorry I misread your post. Ok, so you have added another article back > in. IIRC if you do this through the wizard the entire snapshot will be > generated. If you do it through query analyzer only the added article will > be resnapshotted if you are using named subscriptions. If you are using > anonymous the entire publication will be resnapshotted. > > The force_invalidate_snapshot option will bypass a warning message if the > change you are making to the publication will break the snapshot and > require a new one. If you set this to 0 the procs will raise an error > message and the proc will not do its task. If you set it to 1 no message > will be raised and the snapshot will be required. > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Jude" <judes@email.uophx.edu> wrote in message > news:%235lEil94GHA.696@TK2MSFTNGP06.phx.gbl... >> How can I stop the entire snapshot from being generated now & only get >> that one table snapshot? >> >> When I started the Snapshot agent the entire snapshot was being generated >> again & I stopped the agent. >> >> By the way, when it says I have to "force invalidate snapshot" am I >> correct in putting @Force_Invalidate = 1? >> >> -- >> JUDE >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> news:%23d1XEo74GHA.2536@TK2MSFTNGP06.phx.gbl... >>> Hi Jude >>> >>> You did nothing wrong. What you perhaps could do is remove the contents >>> of the stored procedure from the article you wish to "drop". This way it >>> will effectively be dropped - in other words the commands won't be >>> applied, but changes will be tracked and the command constructed for it. >>> >>> -- >>> Hilary Cotter >>> Director of Text Mining and Database Strategy >>> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. >>> >>> This posting is my own and doesn't necessarily represent RelevantNoise's >>> positions, strategies or opinions. >>> >>> Looking for a SQL Server replication book? >>> http://www.nwsu.com/0974973602.html >>> >>> Looking for a FAQ on Indexing Services/SQL FTS >>> http://www.indexserverfaq.com >>> >>> >>> >>> "Jude" <judes@email.uophx.edu> wrote in message >>> news:OS6ELww4GHA.696@TK2MSFTNGP06.phx.gbl... >>> Sql Server 2000 to Sql Server 2000 Transactional Replication - On Same >>> Domain >>> No Anonymous Subscribers >>> Nothing Fancy >>> >>> Using Sql Query Analyzer (Got burnt by making the change at EM & having >>> entire snapshot being invalidated once) >>> >>> Script = Sp_droparticle - said I had to force invalidate snapshot >>> >>> But after adding the article back & then starting the Snapshot agent, >>> instead of seeing a snapshot for just that one article, I am seeing the >>> entire snapshot being generated again. >>> >>> Where have I gone wrong? Do I have something set incorrectly? I don't >>> want a full snapshot to be generated every time I make a change. Any >>> way to back door that & have only the one table marked to be snapshot? >>> >>> -- >>> JUDE >>> >> >> > >
Perhaps your publication allows anonymous subscribers? In this case the old
snapshot will be invalidated to future subscribers. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com .
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 |