|
|
You're in the
sql server replication
group:Deleting Large Quantiy of Rows
sql server replication:
only and the data flow is only from the publisher to the subscriber for this table. If so remove this table from the merge publication, put it in a transactional publication and do your deletes through a stored procedure and replicate the execution of the stored procedure. -- Hilary Cotter 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] "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message news:%23kd7psfrFHA.3604@tk2msftngp13.phx.gbl... > Hi Guys, > > I need a little advice. I need to delete 250000 rows on a monthly basis and > my users are using MSDE 2000 with merge replication, publisher is SQL Server > 2000 Standard. > > The users will never be uploading or making changes to this table. Is there > any way i can make this a quick delete as currently for each row that is in > the Article published table sql is sending down a delete statement for each > row to the subscriber. Thus taking longer than expected. > > Any ideas or advice would be greatly apprecitaed. > > Thanks, Tim. > >
Hi Guys,
I need a little advice. I need to delete 250000 rows on a monthly basis and my users are using MSDE 2000 with merge replication, publisher is SQL Server 2000 Standard. The users will never be uploading or making changes to this table. Is there any way i can make this a quick delete as currently for each row that is in the Article published table sql is sending down a delete statement for each row to the subscriber. Thus taking longer than expected. Any ideas or advice would be greatly apprecitaed. Thanks, Tim.
I think your best option would be to drop the subscription (possibly drop
the publication as well to drop the triggers which will slow the delete), do the delete, and then recreate the publication and subscription and do a no sync. -- Hilary Cotter 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] "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message news:eSsLlVhrFHA.3720@TK2MSFTNGP14.phx.gbl... > Hi Hilary, > > Thanks for your response, this is not going to be possible as we use the > ActiveX control and the publications have been hard coded. Which i know is > not good. Is there any other way that we could perhaps specify the order > that things get run in I.E sp_AddScriptexec. I have worked a way out with > the system tables that we could remove generations. However i would need to > make sure that sp_addscriptexec was fired first in the replication process. > > Thanks, Tim. > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:%23boP2ShrFHA.1788@tk2msftngp13.phx.gbl... > > From what you are saying it looks like these rows on the subscriber are > > read > > only and the data flow is only from the publisher to the subscriber for > > this > > table. If so remove this table from the merge publication, put it in a > > transactional publication and do your deletes through a stored procedure > > and > > replicate the execution of the stored procedure. > > > > -- > > Hilary Cotter > > 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 > > "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message > > news:%23kd7psfrFHA.3604@tk2msftngp13.phx.gbl... > >> Hi Guys, > >> > >> I need a little advice. I need to delete 250000 rows on a monthly basis > > and > >> my users are using MSDE 2000 with merge replication, publisher is SQL > > Server > >> 2000 Standard. > >> > >> The users will never be uploading or making changes to this table. Is > > there > >> any way i can make this a quick delete as currently for each row that is > > in > >> the Article published table sql is sending down a delete statement for > > each > >> row to the subscriber. Thus taking longer than expected. > >> > >> Any ideas or advice would be greatly apprecitaed. > >> > >> Thanks, Tim. > >> > >> > > > > > >
Hi Hilary,
Thanks for your response, this is not going to be possible as we use the ActiveX control and the publications have been hard coded. Which i know is not good. Is there any other way that we could perhaps specify the order that things get run in I.E sp_AddScriptexec. I have worked a way out with the system tables that we could remove generations. However i would need to make sure that sp_addscriptexec was fired first in the replication process. Thanks, Tim. [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:%23boP2ShrFHA.1788@tk2msftngp13.phx.gbl... > From what you are saying it looks like these rows on the subscriber are > read > only and the data flow is only from the publisher to the subscriber for > this > table. If so remove this table from the merge publication, put it in a > transactional publication and do your deletes through a stored procedure > and > replicate the execution of the stored procedure. > > -- > Hilary Cotter > 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 > "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message > news:%23kd7psfrFHA.3604@tk2msftngp13.phx.gbl... >> Hi Guys, >> >> I need a little advice. I need to delete 250000 rows on a monthly basis > and >> my users are using MSDE 2000 with merge replication, publisher is SQL > Server >> 2000 Standard. >> >> The users will never be uploading or making changes to this table. Is > there >> any way i can make this a quick delete as currently for each row that is > in >> the Article published table sql is sending down a delete statement for > each >> row to the subscriber. Thus taking longer than expected. >> >> Any ideas or advice would be greatly apprecitaed. >> >> Thanks, Tim. >> >> > >
It would remain there. This is probably not what you want, so you would have
to delete on both sides. -- Hilary Cotter 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] "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message news:OBtaphsrFHA.240@tk2msftngp13.phx.gbl... > Hi Hilary, > > Thanks for that. What would happen to the information that was in the table > on the subscriber?? Would that get deleted locally, as this information > would no longer be needed. > > Again Thanks for all you help. > > Tim. > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:%23HJ2hOjrFHA.2592@TK2MSFTNGP09.phx.gbl... > >I think your best option would be to drop the subscription (possibly drop > > the publication as well to drop the triggers which will slow the delete), > > do > > the delete, and then recreate the publication and subscription and do a no > > sync. > > > > -- > > Hilary Cotter > > 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 > > "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message > > news:eSsLlVhrFHA.3720@TK2MSFTNGP14.phx.gbl... > >> Hi Hilary, > >> > >> Thanks for your response, this is not going to be possible as we use the > >> ActiveX control and the publications have been hard coded. Which i know > >> is > >> not good. Is there any other way that we could perhaps specify the order > >> that things get run in I.E sp_AddScriptexec. I have worked a way out with > >> the system tables that we could remove generations. However i would need > > to > >> make sure that sp_addscriptexec was fired first in the replication > > process. > >> > >> Thanks, Tim. > >> > >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > >> news:%23boP2ShrFHA.1788@tk2msftngp13.phx.gbl... > >> > From what you are saying it looks like these rows on the subscriber are > >> > read > >> > only and the data flow is only from the publisher to the subscriber for > >> > this > >> > table. If so remove this table from the merge publication, put it in a > >> > transactional publication and do your deletes through a stored > >> > procedure > >> > and > >> > replicate the execution of the stored procedure. > >> > > >> > -- > >> > Hilary Cotter > >> > 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 > >> > "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message > >> > news:%23kd7psfrFHA.3604@tk2msftngp13.phx.gbl... > >> >> Hi Guys, > >> >> > >> >> I need a little advice. I need to delete 250000 rows on a monthly > >> >> basis > >> > and > >> >> my users are using MSDE 2000 with merge replication, publisher is SQL > >> > Server > >> >> 2000 Standard. > >> >> > >> >> The users will never be uploading or making changes to this table. Is > >> > there > >> >> any way i can make this a quick delete as currently for each row that > > is > >> > in > >> >> the Article published table sql is sending down a delete statement for > >> > each > >> >> row to the subscriber. Thus taking longer than expected. > >> >> > >> >> Any ideas or advice would be greatly apprecitaed. > >> >> > >> >> Thanks, Tim. > >> >> > >> >> > >> > > >> > > >> > >> > > > > > >
Hi Hilary,
Thanks for that. What would happen to the information that was in the table on the subscriber?? Would that get deleted locally, as this information would no longer be needed. Again Thanks for all you help. Tim. [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:%23HJ2hOjrFHA.2592@TK2MSFTNGP09.phx.gbl... >I think your best option would be to drop the subscription (possibly drop > the publication as well to drop the triggers which will slow the delete), > do > the delete, and then recreate the publication and subscription and do a no > sync. > > -- > Hilary Cotter > 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 > "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message > news:eSsLlVhrFHA.3720@TK2MSFTNGP14.phx.gbl... >> Hi Hilary, >> >> Thanks for your response, this is not going to be possible as we use the >> ActiveX control and the publications have been hard coded. Which i know >> is >> not good. Is there any other way that we could perhaps specify the order >> that things get run in I.E sp_AddScriptexec. I have worked a way out with >> the system tables that we could remove generations. However i would need > to >> make sure that sp_addscriptexec was fired first in the replication > process. >> >> Thanks, Tim. >> >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> news:%23boP2ShrFHA.1788@tk2msftngp13.phx.gbl... >> > From what you are saying it looks like these rows on the subscriber are >> > read >> > only and the data flow is only from the publisher to the subscriber for >> > this >> > table. If so remove this table from the merge publication, put it in a >> > transactional publication and do your deletes through a stored >> > procedure >> > and >> > replicate the execution of the stored procedure. >> > >> > -- >> > Hilary Cotter >> > 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 >> > "Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message >> > news:%23kd7psfrFHA.3604@tk2msftngp13.phx.gbl... >> >> Hi Guys, >> >> >> >> I need a little advice. I need to delete 250000 rows on a monthly >> >> basis >> > and >> >> my users are using MSDE 2000 with merge replication, publisher is SQL >> > Server >> >> 2000 Standard. >> >> >> >> The users will never be uploading or making changes to this table. Is >> > there >> >> any way i can make this a quick delete as currently for each row that > is >> > in >> >> the Article published table sql is sending down a delete statement for >> > each >> >> row to the subscriber. Thus taking longer than expected. >> >> >> >> Any ideas or advice would be greatly apprecitaed. >> >> >> >> Thanks, Tim. >> >> >> >> >> > >> > >> >> > >
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 |