Help with a large delete

I have a table that is part a merge publication that I need to delete 3
million rows from which will leave about a million in the table. I plan to
just insert a list of the id's to go in a temporary table and then just do
delete where id in table X.
Another way that has been suggested to me is to place a copy of the records
that I want to keep into another table and then truncate the main table and
then put the ones I want back in. Would this method work due to the table
being part of a merge publication, as I presume that the truncate would not
happen on the server that is subscribed to this publication.
I'd do the truncate and reinsert as your transaction log will likely grow
absolutely huge the other way. Not to say it won't grow huge the first way.
keep in mind that in order to do the truncate you will need to drop the
subscriptions and publications.
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
"Russell" <Russell@.discussions.microsoft.com> wrote in message
news:F3DE3D1A-A230-4E87-B23D-79CA1B2F8460@.microsoft.com...
> I have a table that is part a merge publication that I need to delete 3
> million rows from which will leave about a million in the table. I plan to
> just insert a list of the id's to go in a temporary table and then just do
> delete where id in table X.
> Another way that has been suggested to me is to place a copy of the
records
> that I want to keep into another table and then truncate the main table
and
> then put the ones I want back in. Would this method work due to the table
> being part of a merge publication, as I presume that the truncate would
not
> happen on the server that is subscribed to this publication.
|||Will it only grow huge on the server that I do the delete on or will it grow
huge on both servers?
"Hilary Cotter" wrote:

> I'd do the truncate and reinsert as your transaction log will likely grow
> absolutely huge the other way. Not to say it won't grow huge the first way.
> keep in mind that in order to do the truncate you will need to drop the
> subscriptions and publications.
> --
> 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
> "Russell" <Russell@.discussions.microsoft.com> wrote in message
> news:F3DE3D1A-A230-4E87-B23D-79CA1B2F8460@.microsoft.com...
> records
> and
> not
>
>