I've been unable to find an answer to this, despite reading various conflicting articles. I'll try to keep it simple:
Lets say need to import 1 million rows of data, totaling 10GB in size.
Use SSIS Fast load, with MICS as 100k (so 1GB)
This will then send off 10x 100K rows to log file
This still causes log file to grow to 10GB as per MSDN (stating that it treats it as Batch_Size as per BULK Load, and "Specifies the number of rows in a batch. Each batch is copied to the server as one transaction. If this fails, SQL Server commits or rolls back the transaction for every batch. By default, all data in the specified data file is one batch. For information about performance considerations, see "Remarks," later in this topic.")
So given that all transaction of 100k will be rolled back should a failure occur at any point (i've tested this and its true), is the only real way to stop the log file growing batch up the records using something like a FELC?
Lets say need to import 1 million rows of data, totaling 10GB in size.
Use SSIS Fast load, with MICS as 100k (so 1GB)
This will then send off 10x 100K rows to log file
This still causes log file to grow to 10GB as per MSDN (stating that it treats it as Batch_Size as per BULK Load, and "Specifies the number of rows in a batch. Each batch is copied to the server as one transaction. If this fails, SQL Server commits or rolls back the transaction for every batch. By default, all data in the specified data file is one batch. For information about performance considerations, see "Remarks," later in this topic.")
So given that all transaction of 100k will be rolled back should a failure occur at any point (i've tested this and its true), is the only real way to stop the log file growing batch up the records using something like a FELC?