Posts Tagged ‘problems’


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


One of the problems with moving a SQL insert statement to SSIS based packages is that logic which is freely available in SQL needs some work arounds to get the same result in SSIS. Such work arounds needs to be developed when working with pattern matching. In SQL, doing pattern matching is fairly easy. We may match patterns for logical tests using the SQL LIKE clause as follows: ...,[SLAM_HRG_Code] = CASE WHEN LEFT(r.[Service],1) LIKE '[A-Za-z]' AND SUBSTRING(r.[Service],2,1) LIKE '[A-Za-z]' AND ISNUMERIC(SUBSTRING(r.[Service],3,2))


Top 10 things to watch out for in a data migration project

When undergoing a data migration, from one system to another, or from one database format to another, there are a number of common issues which crop up.  Any of these can cause the migration to fail.   These issues can be mitigated by careful planning before starting the migration project, and by comprehensive testing before the migration is signed off as complete. The top 10 data migration issues most likely to cause