Hi,
We used to have a clustered index which consisted of 5 fields, this was ordered incorrectly which meant new inserts caused a lot of bad page splits.
This CI was reordered to be correct and that composite (5 fields) key would now be always ascending therefore it will not insert anything in between the pages.
I confirmed that there were minimal page splits via the transaction logs. However the inserts now are taking approximately 10 times longer than before.
There was an additional non-clustered index put in to cover for scenarios that the new CI doesn't cover, this is causing some new page splits, however I doubt that the non-clustered index page splits cause that much of a difference.
I use SSIS OLE DB Destination with Fast Load & Check Constraints Options.
Any idea what would be the issue, or what I should look at?