The (commonly referred to as the SSDA903 or the "903 return") is a statutory annual data collection required by the UK Department for Education (DfE). It is a critical reporting mechanism for all local authorities in England to provide detailed individual-level information about children looked after (CLA) and care leavers. What is the SSIS 903?
The search may also relate to the legacy package deployment model in contrast with the newer project deployment model, but this topic is much less common. Most frequently, the term is used by database administrators and ETL developers encountering the 0xC0209303 error during package execution. For this reason, this guide will focus primarily on the error code, providing a definitive resource for understanding and fixing it.
A full 903 record is not a single file but a collection of structured data "episodes."
Ensure your SQL Server Agent jobs are explicitly configured to run packages in 64-bit mode, unless you are strictly bound to a 32-bit legacy Excel/Access data source.
Create a account that uses this credential to run SQL Server Integration Services packages.
The error 0xC0010009 (sometimes associated with DTS_E_CANTCHANGE ) commonly appears as:
While 0xC0010008 (Package description too long) or 0xC0202009 (OLE DB Error) are common, the or 0xC020903 —often surfacing as an DTS_E_INVALIDCOLUMN or an ODBC/OLE DB failure—points to a discrepancy between your metadata and the actual data flow. This article dives into troubleshooting and fixing these elusive 903-type errors. What is the SSIS 903 Error?
SSIS 903: Navigating the Statutory Return for Children Looked After 1. Understanding the 903 Requirement
To ensure your ETL pipelines remain resilient against metadata and database engine errors, implement these structural habits:
For detailed technical manuals and step-by-step fiscal instructions, you should refer to your specific state's portal:
What is the of the error message shown in your SSIS execution log?
Never rely on a single point of failure. In your package design, anticipate that file paths might be missing or a connection might be down.
Schedule weekly DBCC CHECKDB jobs on all transactional databases and the SSISDB catalog to catch index corruption before it halts your ETL processes.