When is enabled, the OnInformation event now includes messages such as:
When the refreshed at 09:00, the CFO smiled at the fresh numbers. A quick note from Jenna arrived in the team Slack channel: ssis-948
The error code was notorious in the team’s lore—a cryptic, intermittent fault that had haunted the “Daily Sales Load” package for months. It usually manifested only during the early hours of the morning, when the data volume spiked and the source system was still catching up from the previous night’s batch. When is enabled, the OnInformation event now includes
Result: The runtime automatically grew buffers to (≈ 9 000 rows) once it detected average row size ~10 KB, cutting the number of I/O calls by ~30 % and halving the overall load time. Result: The runtime automatically grew buffers to (≈
In this blog post, we covered the basics of the SSIS-948 error code, its possible causes, and troubleshooting steps. By understanding the root cause of the issue and applying the suggested solutions, you should be able to resolve the error and continue working with your SSIS packages.
Instead of halting the entire package on a few bad rows, Jenna changed the of the OLE DB Destination to Redirect Row . The redirected rows would be written to a quarantine table dbo.FactSales_Rejected for later investigation, and the package would continue loading the good data.