February 7, 2005 at 8:11 am
....
February 7, 2005 at 4:02 pm
I don't believe the BCP has a published limit to the number of rows it can handle. I know that I have used it to handle a table with over 135 million rows, and I routinely handle tables with 10 -30 million rows with it...
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
February 7, 2005 at 7:14 pm
If this is "a direct insert from one table to another", why is BCP involved?
If you are importing data into the table from another source, then again, why is BCP involved?
In SQL Server 2000, where the DTS datapump or T-SQL INSERT statements don't provide the performance, or capability that's needed, you should use BULK INSERT, not BCP.
--------------------
Colt 45 - the original point and click interface
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply