Posts Tagged ‘error’


When loading data through an SSIS package, one of the problems we face is when data causes a step to fail.  If the source data contains 10,000 rows, how do we tell which row had the data that was too long, in the wrong format, null or caused the bad join? Well, when running in automated mode (via a SQL agent job), SQL will log the cause of the error (the error description and the column), but will not log anything


There is a bug in SQL Server 2008 and 2005.  When you try and link a 64 bit server to a 32 bit server, the select of data can fail.   But the fail is not obvious. When you say "select * from linkedserver.mydbname.dbo.table" it will return a message about stored procedures such as: The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator. This is because


Whenever we develop data maintenance packages through SSIS for our customers, one of the areas we pay particular attention to are invalid records. Where possible, we work with the owner of the data to put in code to cleanse the data as it is processed, but for unexpected errors, we like to create customer logging and error trapping, which processes the valid data, logs the invalid data (for manual entry or correction), and continues without failing the who