Use parallel bulk copy to copy data in parallel to a specific partition. Parallel bulk copy substantially increases performance during bcp sessions because it can split large bulk copy jobs into multiple sessions and run the sessions concurrently.
sp_helpartition – to see the number of partitions on the table.
alter table ... partition – to partition the table, if the table is not already partitioned.
If the table has a clustered index, this index determines the physical placement of the data, causing the partition specification in the bcp command to be ignored.
If any indexes exist, bcp automatically uses its slow bulk copy instead of its fast bulk copy mode.
If nonclustered indexes exist on the tables, parallel bulk copy is likely to lead to deadlocks on index pages.
Each partition should reside on a separate physical disk for the best performance.
Before you copy data into your database, partition the table destined to contain the data.
bcp tablename partition partition_name in file_name
bcp tablename partition_number in file_name
See the Transact-SQL Users Guide for information about partitioning a table.