Is SSIS (2008r2) capable of performing a minimally logged insert into an empty table with a clustered index?
I'm aware of the prerequisites for a minimally logged insert. This is more about how ssis buffers affect the batch size.
My db is in simple recovery mode.
my oledb destination is set to table - fast load with table lock selected (everything else unchecked) and the rows per batch and maximum insert commit size left to the default. This to me seems like it achieves all the requirements. Empty destination table, insert in one transaction.
But doesn't the data flow's default max buffer rows in reality batch up the insert? so only the first 10,000 rows /10 megs is minimally logged and the rest are fully logged? This is what i'm seeing when I look at the table (sp_spaceused - row size and index size gradually increasing), and sp_who2 also shows an incrementing LastBatch date. Plus the rows/sec is gradually decreasing over time.
Is there a way around this other than dropping/recreating the indexes? Does specifying the ORDER() keep it minimally logged for the entire load or does it just alleviate the index sort?
Jakub @ Adelaide, Australia