Use bcp with a small batch size, like 1000. Also use the bulk insert
recovery model.
--
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] "Murali" <Murali@discussions.microsoft.com> wrote in message
news:C5385B3D-4D88-4284-9C2B-DBD36D0F3AF9@microsoft.com...
> Hi,
> We are uploading data from one table to another table. Table size is 430
> million rows. We are using INSERT INTO .. for bulkloading. The problem we
> are
> facing is transaction log becomes too huge and unmanageable once we
> complete
> this operation. I want to know is there a way we could turn off the
> transaction log just for the duration(session) we execute this command.
> Any
> other approaches are welcome.
> Regards,
> Murali